← previous blocknext block →recent activity
Analyzing
Block #94,973,899
10 transactions · 9 stateful · 2026-08-11 05:07:41 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,973,899 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xd30f9e74…d404
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xedef8de7…eee6
0x065c9d…c394
4 touches
1 conflict
0x503e3469…c8b8
0x065c9d…c394
2 touches
0 conflicts
0x5831fe27…2f9d
0x065c9d…c394
2 touches
0 conflicts
0x66c6a3df…a298
0x065c9d…c394
2 touches
0 conflicts
0xa41dfe3d…57ac
0x065c9d…c394
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
1 conflict on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity