← previous blocknext block →recent activity
Analyzing
Block #95,393,138
10 transactions · 9 stateful · 2026-08-12 16:29:57 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,393,138 · 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
2w03w15w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7d8244…74a9
0x34b655…2a6f
4 touches
1 conflict
0x224d6800…4508
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x4e621c19…6089
0x34b655…2a6f
3 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
2 touches
0 conflicts
0x336fbcc7…60a7
0x34b655…2a6f
2 touches
0 conflicts
0x3e6302c8…64f5
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 0x1c7d824489…6c74a9
Audit this contract →
← previous block·next block →recent activity