← previous blocknext block →recent activity
Analyzing
Block #95,726,277
21 transactions · 20 stateful · 2026-08-13 20:27:31 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,726,277 · 21 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
1w02w03w04w05w16w29w113w214w315w416w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78bb22fa…26f2
0x34b655…2a6f
12 touches
15 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0x73f2022f…8ba2
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
15 conflicts on slot 0x78bb22fae7…cc26f2
Audit this contract →
← previous block·next block →recent activity