← previous blocknext block →recent activity
Analyzing
Block #101,675,002
12 transactions · 11 stateful · 2026-09-03 17:32:38 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,675,002 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w29w310w011w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8d02208…8db3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8fbc8aa5…8120
0x34b655…2a6f
6 touches
3 conflicts
0x29045a66…403c
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0xc8d022088a…868db3
Audit this contract →
← previous block·next block →recent activity