← previous blocknext block →recent activity
Analyzing
Block #99,624,314
18 transactions · 18 stateful · 2026-08-27 13:22:21 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,624,314 · 18 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
1w02w03w14w15w06w17w08w211w212w313w415w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0203a60f…d0bd
0x34b655…2a6f
6 touches
3 conflicts
0x0db07ef0…b141
0x34b655…2a6f
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb64b9585…6270
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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 0x0203a60f30…64d0bd
Audit this contract →
← previous block·next block →recent activity