← previous blocknext block →recent activity
Analyzing
Block #99,134,812
10 transactions · 9 stateful · 2026-08-25 20:11:38 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,134,812 · 10 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bd6a2cb…a8e5
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x0f8965bb…e238
0x34b655…2a6f
2 touches
0 conflicts
0x13807d54…85db
0x34b655…2a6f
2 touches
0 conflicts
0x4038f924…39a1
0x34b655…2a6f
2 touches
0 conflicts
0x61e68cf7…28b1
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
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 0x2bd6a2cb3d…9ba8e5
Audit this contract →
← previous block·next block →recent activity