← previous blocknext block →recent activity
Analyzing
Block #99,354,426
33 transactions · 30 stateful · 2026-08-26 14:36:34 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,354,426 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w07w18w19w210w111w012w213w014w115w216w323w124w225w027w128w230w131w232w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3c05624…3417
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x47bae1…7568
4 touches
1 conflict
0x00000000…0003
0x47bae1…7568
4 touches
1 conflict
0x00000000…0004
0x47bae1…7568
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
6 conflicts on slot 0xd3c0562470…3e3417
Audit this contract →
← previous block·next block →recent activity