← previous blocknext block →recent activity
Analyzing
Block #99,254,313
23 transactions · 20 stateful · 2026-08-26 06:12:50 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,254,313 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w08w19w110w111w316w218w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe512bd8b…ae5a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0xe98994bf…41f4
0xd32edf…ff58
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0xe512bd8b7a…a7ae5a
Audit this contract →
← previous block·next block →recent activity