← previous blocknext block →recent activity
Analyzing
Block #73,683,773
8 transactions · 8 stateful · 2026-05-10 13:39:08 UTC
Parallelism
38/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,683,773 · 8 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0xa2b460a9…1319
0x065c9d…c394
3 touches
1 conflict
0xff975afd…7f7f
0x065c9d…c394
3 touches
1 conflict
0x14f5a90c…e7d2
0x065c9d…c394
3 touches
1 conflict
0x7f87703e…58c8
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity