← previous blocknext block →recent activity
Analyzing
Block #99,247,219
21 transactions · 20 stateful · 2026-08-26 05:37:09 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,247,219 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w17w210w311w417w220w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf2dc7074…4491
0x34b655…2a6f
6 touches
3 conflicts
0x0dd5cdfa…574f
0x34b655…2a6f
4 touches
1 conflict
0x126c10ea…a328
0x34b655…2a6f
4 touches
1 conflict
0x30c10c87…22ec
0x34b655…2a6f
4 touches
1 conflict
0x49f69157…4445
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity