← previous blocknext block →recent activity
Analyzing
Block #99,354,136
11 transactions · 10 stateful · 2026-08-26 14:35:06 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,354,136 · 11 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
2w03w16w27w38w410w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17ff2059…ddb4
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd704896f…4213
0x34b655…2a6f
4 touches
1 conflict
0xd9c05bd7…8cc8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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 0x17ff2059d7…7addb4
Audit this contract →
← previous block·next block →recent activity