← previous blocknext block →recent activity
Analyzing
Block #94,480,746
13 transactions · 11 stateful · 2026-08-09 11:45:45 UTC
Parallelism
39/100
Blocked
64%
Avg conflicts / tx
2.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,480,746 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
16 touches
28 conflicts
0xd8cbc3be…1349
0x065c9d…c394
15 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
14 touches
21 conflicts
0x6e7bb7b2…df82
0x754704…b603
4 touches
1 conflict
0x7e0b7922…c351
0x754704…b603
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0xf7adce63…0fd2
0x754704…b603
4 touches
1 conflict
0x4c1fbdf6…953d
0x754704…b603
4 touches
1 conflict
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
28 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity