← previous blocknext block →recent activity
Analyzing
Block #101,972,654
11 transactions · 11 stateful · 2026-09-04 18:33:10 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,972,654 · 11 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
3w05w06w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb22303…6db3
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x36918c55…8424
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x3267c710…7e10
0x34b655…2a6f
2 touches
0 conflicts
0x41f84ea8…bcca
0x34b655…2a6f
2 touches
0 conflicts
0xe2125b66…018c
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 0xafb22303eb…7c6db3
Audit this contract →
← previous block·next block →recent activity