← previous blocknext block →recent activity
Analyzing
Block #94,718,302
23 transactions · 19 stateful · 2026-08-10 07:40:35 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,718,302 · 23 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
3w05w06w17w28w39w011w315w016w117w118w419w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcba76693…20ff
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0007
0xc35b1c…298f
8 touches
6 conflicts
0x00000000…000a
0xc35b1c…298f
8 touches
6 conflicts
0x00000000…0003
0xeae24c…0be0
8 touches
6 conflicts
0x00000000…0000
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0001
0xfa32f9…f3f0
8 touches
6 conflicts
0x997ccc40…4dfd
0x3bd359…433a
8 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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: 0xfa32f9ec…fef3f0
6 conflicts on slot 0xcba7669378…7d20ff
Audit this contract →
← previous block·next block →recent activity