← previous blocknext block →recent activity
Analyzing
Block #95,795,611
25 transactions · 23 stateful · 2026-08-14 02:16:13 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,795,611 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w18w210w311w413w414w515w519w220w323w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5a1b2fe…5369
0x34b655…2a6f
10 touches
10 conflicts
0xd895ee0b…d301
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
6 touches
3 conflicts
0xefa65ccf…1078
0x34b655…2a6f
6 touches
3 conflicts
0x0490581d…adaf
0x34b655…2a6f
6 touches
3 conflicts
0xddc0f050…9726
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xc5a1b2febf…f05369
Audit this contract →
← previous block·next block →recent activity