← previous blocknext block →recent activity
Analyzing
Block #94,971,389
10 transactions · 9 stateful · 2026-08-11 04:55:04 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,971,389 · 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
1w05w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x356dcd9c…c286
0x851145…3f07
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xf9312173…41a7
0x851145…3f07
4 touches
1 conflict
0x39977254…07b1
0x2b46c0…1669
2 touches
0 conflicts
0x3a3e7727…36c5
0x2b46c0…1669
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 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity