← previous blocknext block →recent activity
Analyzing
Block #99,490,306
12 transactions · 10 stateful · 2026-08-27 02:00:56 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,490,306 · 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
1w04w05w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69c3830a…a539
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x2095236c…26d6
0x34b655…2a6f
4 touches
1 conflict
0x63016070…64d5
0x34b655…2a6f
4 touches
1 conflict
0x1ccd1b02…31fd
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
0x34b655…2a6f
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 0x69c3830aaa…83a539
Audit this contract →
← previous block·next block →recent activity