← previous blocknext block →recent activity
Analyzing
Block #95,356,626
17 transactions · 16 stateful · 2026-08-12 13:25:05 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,356,626 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w38w410w515w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79f9dfdc…0cc6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca713a22…3083
0x34b655…2a6f
6 touches
3 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0x3d62531f…af25
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b798706…507c
0x34b655…2a6f
4 touches
1 conflict
0x52f3d91c…1822
0x34b655…2a6f
4 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
10 conflicts on slot 0x79f9dfdc8f…c20cc6
Audit this contract →
← previous block·next block →recent activity