← previous blocknext block →recent activity
Analyzing
Block #94,473,383
10 transactions · 8 stateful · 2026-08-09 11:08:43 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,473,383 · 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
4w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaaa210f6…a05e
0x065c9d…c394
5 touches
3 conflicts
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x54474915…9e0b
0x754704…b603
4 touches
1 conflict
0xf2a1c5ca…fde6
0x065c9d…c394
3 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity