← previous blocknext block →recent activity
Analyzing
Block #96,111,965
14 transactions · 14 stateful · 2026-08-15 04:47:54 UTC
Parallelism
50/100
Blocked
64%
Avg conflicts / tx
1.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,111,965 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w410w511w612w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
14 touches
21 conflicts
0xd5d0b681…ca6c
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x991e2e20…94a6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xea290724…08fd
0x34b655…2a6f
6 touches
3 conflicts
0x8f888556…f387
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: 0x59df8637…6d2780
21 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity