← previous blocknext block →recent activity
Analyzing
Block #101,660,402
9 transactions · 8 stateful · 2026-09-03 16:19:10 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,660,402 · 9 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
3w05w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb11940a…519b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x24e14bd1…ebf2
0x34b655…2a6f
4 touches
1 conflict
0x30a65b14…dfe2
0x34b655…2a6f
2 touches
0 conflicts
0x5060cdde…445d
0x34b655…2a6f
2 touches
0 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
2 touches
0 conflicts
0x7c09c53e…64b4
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 0xdb11940a1f…24519b
Audit this contract →
← previous block·next block →recent activity