← previous blocknext block →recent activity
Analyzing
Block #94,047,044
14 transactions · 13 stateful · 2026-08-07 23:08:31 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,047,044 · 14 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
1w02w17w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x4a362bce…f100
0xa6afd3…d132
5 touches
3 conflicts
0x4c1fbdf6…953d
0x754704…b603
4 touches
1 conflict
0x6430e4fc…e73c
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity