← previous blocknext block →recent activity
Analyzing
Block #102,348,245
17 transactions · 17 stateful · 2026-09-06 02:16:51 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,348,245 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w29w311w412w514w615w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x1139b3b1…daf2
0x34b655…2a6f
12 touches
15 conflicts
0x2a565afa…37fc
0x34b655…2a6f
10 touches
10 conflicts
0x1f396cee…862f
0x34b655…2a6f
10 touches
10 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
10 touches
10 conflicts
0x5150abbe…43c3
0x34b655…2a6f
8 touches
6 conflicts
0x04ee2aa4…8e54
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity