← previous blocknext block →recent activity
Analyzing
Block #99,362,402
20 transactions · 17 stateful · 2026-08-26 15:16:50 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,362,402 · 20 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
3w05w07w08w113w114w015w116w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9533afa1…2614
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xd2b36119…e4e1
0x851145…3f07
4 touches
1 conflict
0xe957c63b…e347
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0x71717491…10cf
0xa6afd3…d132
4 touches
1 conflict
0x984d12d6…f0d4
0x34b655…2a6f
4 touches
1 conflict
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 0x9533afa186…6a2614
Audit this contract →
← previous block·next block →recent activity