← previous blocknext block →recent activity
Analyzing
Block #94,982,430
17 transactions · 16 stateful · 2026-08-11 05:50:35 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,982,430 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w28w311w412w513w014w1
- 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
0x0238a690…29bd
0x754704…b603
4 touches
1 conflict
0xa8e98b9f…5935
0x01bff4…1071
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x988b0878…2b82
0x065c9d…c394
4 touches
1 conflict
0xb0e2447c…17dc
0x754704…b603
4 touches
1 conflict
0x4ecaacf7…9b3b
0x065c9d…c394
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
3 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity