← previous blocknext block →recent activity
Analyzing
Block #94,061,945
11 transactions · 11 stateful · 2026-08-08 00:23:26 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,061,945 · 11 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
4w05w16w27w3
- 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
0x0d3dbba6…55eb
0xa6afd3…d132
8 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0x8460b9c1…a196
0x754704…b603
4 touches
1 conflict
0x5261f6ab…9aa1
0xee8c0e…1242
4 touches
1 conflict
0x3040553c…5e28
0x754704…b603
4 touches
1 conflict
0x8e5cc690…b06b
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
6 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity