← previous blocknext block →recent activity
Analyzing
Block #94,980,174
10 transactions · 9 stateful · 2026-08-11 05:39:15 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,980,174 · 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
1w02w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x484b0d1c…9ccd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xc4328d82…54c2
0x34b655…2a6f
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x61b5628d…372b
0x065c9d…c394
2 touches
0 conflicts
0xb0476e2c…d1b5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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: Market-MON/USDC
1 conflict on slot 0x484b0d1cb4…f09ccd
Audit this contract →
← previous block·next block →recent activity