← previous blocknext block →recent activity
Analyzing
Block #99,366,234
22 transactions · 17 stateful · 2026-08-26 15:36:09 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,366,234 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w111w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3c05624…3417
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x17ff2059…ddb4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x57fc1089…facb
0x34b655…2a6f
4 touches
1 conflict
0x168cce20…53ee
0x34b655…2a6f
4 touches
1 conflict
0x855bb14e…792c
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 0xd3c0562470…3e3417
Audit this contract →
← previous block·next block →recent activity