← previous blocknext block →recent activity
Analyzing
Block #99,099,466
12 transactions · 9 stateful · 2026-08-25 17:13:42 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,099,466 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d22c394…c125
0x34b655…2a6f
6 touches
3 conflicts
0x33000c0a…82c3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf326723f…a3f6
0x34b655…2a6f
4 touches
1 conflict
0x69ee34d1…30f8
0x34b655…2a6f
2 touches
0 conflicts
0x71f739c7…4879
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
3 conflicts on slot 0x9d22c394fb…48c125
Audit this contract →
← previous block·next block →recent activity