← previous blocknext block →recent activity
Analyzing
Block #99,607,279
10 transactions · 10 stateful · 2026-08-27 11:54:50 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,607,279 · 10 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
2w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x931975c2…b7b3
0x34b655…2a6f
4 touches
1 conflict
0x5a80aa72…01b2
0x34b655…2a6f
4 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x173df5ef…3917
0x34b655…2a6f
2 touches
0 conflicts
0x1d1b78c2…9055
0x34b655…2a6f
2 touches
0 conflicts
0x2c97e962…ce1d
0x34b655…2a6f
2 touches
0 conflicts
0x6183ee9a…21b1
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity