← previous blocknext block →recent activity
Analyzing
Block #99,120,406
12 transactions · 11 stateful · 2026-08-25 18:59:09 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,120,406 · 12 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
1w02w04w17w18w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aac035d…249c
0x34b655…2a6f
4 touches
1 conflict
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x18fa0669…dc9b
0x065c9d…c394
3 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x5dece9e1…b7a9
0x065c9d…c394
2 touches
0 conflicts
0x81ece02b…1b66
0x065c9d…c394
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 0x2aac035d57…48249c
Audit this contract →
← previous block·next block →recent activity