← previous blocknext block →recent activity
Analyzing
Block #102,488,632
110 transactions · 110 stateful · 2026-09-06 14:08:05 UTC
Parallelism
98/100
Blocked
1%
Avg conflicts / tx
0.01
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,488,632 · 110 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8feb2121…031a
0x34b655…2a6f
4 touches
1 conflict
0x9d7ac3b9…22f8
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0xb3e293fe…be2e
0x34b655…2a6f
4 touches
1 conflict
0xe153342d…ba97
0x34b655…2a6f
4 touches
1 conflict
0xf635cede…952d
0x34b655…2a6f
4 touches
1 conflict
0x3a00bc76…abaf
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity