← previous blocknext block →recent activity
Analyzing
Block #99,953,416
22 transactions · 18 stateful · 2026-08-28 17:05:44 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,953,416 · 22 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
1w04w17w08w115w218w119w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dd2a831…bd5d
0x34b655…2a6f
4 touches
1 conflict
0x998fcfe6…acf9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0x4dd2a8311d…52bd5d
Audit this contract →
← previous block·next block →recent activity