← previous blocknext block →recent activity
Analyzing
Block #94,307,287
10 transactions · 9 stateful · 2026-08-08 21:04:45 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,307,287 · 10 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
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf13704e6…258a
0xee8c0e…1242
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x5da439f4…df99
0x754704…b603
4 touches
1 conflict
0x5a11cbb2…5103
0xa6afd3…d132
4 touches
1 conflict
0x2d295d92…0bff
0x754704…b603
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity