← previous blocknext block →recent activity
Analyzing
Block #99,490,325
67 transactions · 66 stateful · 2026-08-27 02:01:02 UTC
Parallelism
97/100
Blocked
3%
Avg conflicts / tx
0.03
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,490,325 · 67 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
1w03w162w063w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xff7ebd61…d88a
0x34b655…2a6f
3 touches
1 conflict
0xc8acfae2…0b06
0x34b655…2a6f
3 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0xf39fc031…1675
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 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity