← previous blocknext block →recent activity
Analyzing
Block #102,189,970
12 transactions · 11 stateful · 2026-09-05 12:54:51 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,189,970 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x256918f1…c4d0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd7668c61…55f8
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a8d4a89…7164
0x34b655…2a6f
4 touches
1 conflict
0x60a4a9a9…b398
0x34b655…2a6f
4 touches
1 conflict
0x93109a16…4f3e
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x256918f186…59c4d0
Audit this contract →
← previous block·next block →recent activity