← previous blocknext block →recent activity
Analyzing
Block #95,714,470
14 transactions · 14 stateful · 2026-08-13 19:28:04 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,714,470 · 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
1w02w04w15w29w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x620b761c…270e
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc782ec05…5bb2
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc6b1d981…1be2
0xa6afd3…d132
4 touches
1 conflict
0x57ab060f…974c
0xa6afd3…d132
3 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 0x620b761c50…c2270e
Audit this contract →
← previous block·next block →recent activity