← previous blocknext block →recent activity
Analyzing
Block #95,713,328
17 transactions · 17 stateful · 2026-08-13 19:22:17 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,713,328 · 17 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
3w04w15w16w27w310w411w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5c6ca46…0fcb
0x968279…9342
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x0c32144b…7f1b
0x968279…9342
8 touches
6 conflicts
0x0c32144b…7f1c
0x968279…9342
8 touches
6 conflicts
0x0c32144b…7f1e
0x968279…9342
8 touches
6 conflicts
0xa5c6ca46…0fc5
0x968279…9342
8 touches
6 conflicts
0xa5c6ca46…0fc6
0x968279…9342
8 touches
6 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: 0x96827978…f09342
6 conflicts on slot 0xa5c6ca460a…ad0fcb
Audit this contract →
← previous block·next block →recent activity