← previous blocknext block →recent activity
Analyzing
Block #95,541,046
12 transactions · 12 stateful · 2026-08-13 04:54:48 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,541,046 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2b37cdc…e470
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x4947e67f…aa39
0x34b655…2a6f
6 touches
3 conflicts
0x28f6f56e…2bfd
0x34b655…2a6f
5 touches
3 conflicts
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
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
3 conflicts on slot 0xc2b37cdc32…c4e470
Audit this contract →
← previous block·next block →recent activity