← previous blocknext block →recent activity
Analyzing
Block #99,451,164
19 transactions · 18 stateful · 2026-08-26 22:43:50 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,451,164 · 19 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5b0a4a66…f1cd
0x34b655…2a6f
4 touches
1 conflict
0x3a0ea57c…e67f
0x34b655…2a6f
2 touches
0 conflicts
0x70986451…c6bd
0x34b655…2a6f
2 touches
0 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
2 touches
0 conflicts
0xa5b4eb1b…616b
0x34b655…2a6f
2 touches
0 conflicts
0xea7754dd…b1b9
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 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity