← previous blocknext block →recent activity
Analyzing
Block #102,234,876
16 transactions · 14 stateful · 2026-09-05 16:42:17 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,234,876 · 16 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
1w02w16w112w013w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x1a2e73cf…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x240838f0…5b9e
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6e4e6f83…8a7c
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
1 conflict on slot 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity