← previous blocknext block →recent activity
Analyzing
Block #101,663,484
13 transactions · 13 stateful · 2026-09-03 16:34:41 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,663,484 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w110w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2100c034…b5d0
0x34b655…2a6f
3 touches
1 conflict
0x0e8c6a13…ecff
0x34b655…2a6f
3 touches
1 conflict
0x1db307e5…8772
0x34b655…2a6f
2 touches
0 conflicts
0x23d02682…70b3
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
3 conflicts on slot 0x9b4f173cee…8c94e6
Audit this contract →
← previous block·next block →recent activity