← previous blocknext block →recent activity
Analyzing
Block #101,500,554
11 transactions · 8 stateful · 2026-09-03 02:55:02 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,500,554 · 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
2w03w14w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a95f394…be66
0x34b655…2a6f
4 touches
1 conflict
0xb891e8a8…7f63
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x18734cd0…c4ac
0x34b655…2a6f
2 touches
0 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
2 touches
0 conflicts
0x39c9ba4d…c485
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 0x5a95f394d8…29be66
Audit this contract →
← previous block·next block →recent activity