← previous blocknext block →recent activity
Analyzing
Block #73,161,380
8 transactions · 7 stateful · 2026-05-08 03:38:07 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,161,380 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4e06760f…7650
0x065c9d…c394
2 touches
0 conflicts
0x9f6ac4f5…6f7a
0x065c9d…c394
2 touches
0 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
2 touches
0 conflicts
0xa9988419…9f45
0x34b655…2a6f
2 touches
0 conflicts
0xd895ee0b…d301
0x34b655…2a6f
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity