← previous blocknext block →recent activity
Analyzing
Block #94,901,624
14 transactions · 12 stateful · 2026-08-10 23:04:11 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,901,624 · 14 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
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xe3285a0a…2b94
0x851145…3f07
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0a471501…8bb1
0x065c9d…c394
2 touches
0 conflicts
0x0ab5c098…96d4
0x065c9d…c394
2 touches
0 conflicts
0x60ae8df9…2c09
0x065c9d…c394
2 touches
0 conflicts
0x770256d0…633f
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