← previous blocknext block →recent activity
Analyzing
Block #94,061,401
8 transactions · 7 stateful · 2026-08-08 00:20:41 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,061,401 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x9149e25a…8c58
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8e46a5d9…ebef
0x065c9d…c394
2 touches
0 conflicts
0xac6cbd24…b086
0x065c9d…c394
2 touches
0 conflicts
0x0778475b…bd75
0x2a68ba…90c5
2 touches
0 conflicts
0x02999939…3b5c
0x34b655…2a6f
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