← previous blocknext block →recent activity
Analyzing
Block #95,710,160
14 transactions · 10 stateful · 2026-08-13 19:06:14 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,710,160 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w17w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0x7c74a8d0…b3ae
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0xf3e174c4…c50f
0xd32edf…ff58
3 touches
1 conflict
0xa43eb5b7…d2ff
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0x4a39a2a411…a6857b
Audit this contract →
← previous block·next block →recent activity