← previous blocknext block →recent activity
Analyzing
Block #99,959,524
25 transactions · 24 stateful · 2026-08-28 17:36:30 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,959,524 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w08w111w212w314w415w117w018w119w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf21a1945…fc5e
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x13857c98…0cc6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
6 touches
3 conflicts
0x0d771e4f…1db7
0x40c49f…2af0
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0xf21a1945ad…9ffc5e
Audit this contract →
← previous block·next block →recent activity