← previous blocknext block →recent activity
Analyzing
Block #95,976,139
10 transactions · 8 stateful · 2026-08-14 17:24:35 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,976,139 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x626b6407…48de
0x34b655…2a6f
6 touches
3 conflicts
0x5ff97156…a075
0x34b655…2a6f
6 touches
3 conflicts
0xcb0221be…c2b3
0x34b655…2a6f
4 touches
1 conflict
0xebf8c5fb…bf2e
0x34b655…2a6f
4 touches
1 conflict
0xfc8cd993…5c11
0x34b655…2a6f
4 touches
1 conflict
0x93f1d5e2…928f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xfe65bb7b2d…7112d7
Audit this contract →
← previous block·next block →recent activity