← previous blocknext block →recent activity
Analyzing
Block #93,550,314
16 transactions · 14 stateful · 2026-08-06 05:30:30 UTC
Parallelism
75/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,550,314 · 16 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
5w06w17w29w3
- 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
6 touches
3 conflicts
0x1e7d5583…f5aa
0x065c9d…c394
3 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x09d00b66…8dea
0x1efe02…37d6
2 touches
0 conflicts
0xc729fb65…d08d
0x1efe02…37d6
2 touches
0 conflicts
0xeec0267b…723d
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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