← previous blocknext block →recent activity
Analyzing
Block #99,485,011
13 transactions · 12 stateful · 2026-08-27 01:34:17 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,485,011 · 13 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
4w07w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8b2cd04…1888
0x34b655…2a6f
4 touches
1 conflict
0x2202504e…fad0
0x34b655…2a6f
4 touches
1 conflict
0x36918c55…8424
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
2 touches
0 conflicts
0x2b6e2a61…3dae
0x34b655…2a6f
2 touches
0 conflicts
0x55010ec8…ea31
0x34b655…2a6f
2 touches
0 conflicts
0x67b854bc…bc4d
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 0xb8b2cd047e…8c1888
Audit this contract →
← previous block·next block →recent activity