← previous blocknext block →recent activity
Analyzing
Block #95,713,286
6 transactions · 6 stateful · 2026-08-13 19:22:05 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,713,286 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2e641595…ce8d
0x34b655…2a6f
2 touches
0 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
2 touches
0 conflicts
0x5e7e0120…7bb9
0x34b655…2a6f
2 touches
0 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
2 touches
0 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity