← previous blocknext block →recent activity
Analyzing
Block #94,903,954
13 transactions · 11 stateful · 2026-08-10 23:15:54 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,903,954 · 13 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
2w03w15w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x1e1c0a81…f84a
0x065c9d…c394
5 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3040553c…5e28
0x754704…b603
4 touches
1 conflict
0xf35f8153…638b
0x754704…b603
4 touches
1 conflict
0x19b340df…f4f0
0x34b655…2a6f
2 touches
0 conflicts
0x1a04fff3…c30a
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