← previous blocknext block →recent activity
Analyzing
Block #95,548,721
16 transactions · 14 stateful · 2026-08-13 05:33:24 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,548,721 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w010w411w512w613w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca713a22…3083
0x34b655…2a6f
12 touches
15 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0x7523c6af…ea66
0x34b655…2a6f
10 touches
10 conflicts
0x52f3d91c…1822
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641e
0x34b655…2a6f
10 touches
10 conflicts
0x461a6b26…d349
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xca713a22d6…9a3083
Audit this contract →
← previous block·next block →recent activity