← previous blocknext block →recent activity
Analyzing
Block #99,454,576
12 transactions · 12 stateful · 2026-08-26 23:01:01 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,454,576 · 12 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
1w02w03w16w27w19w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e1c65d0…77a3
0x34b655…2a6f
4 touches
1 conflict
0xad80ed3d…c92a
0x34b655…2a6f
4 touches
1 conflict
0xb6c92107…e6d7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf08acbb9…a46f
0x34b655…2a6f
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 0x9e1c65d07e…4077a3
Audit this contract →
← previous block·next block →recent activity