← previous blocknext block →recent activity
Analyzing
Block #73,807,970
7 transactions · 6 stateful · 2026-05-11 03:36:39 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,807,970 · 7 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87614c8e…bbd9
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x10531320…3107
0x065c9d…c394
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x61aeb3e1…06b5
0x065c9d…c394
2 touches
0 conflicts
0xa295e8d1…5a55
0x065c9d…c394
2 touches
0 conflicts
0xafccc97b…dfcc
0x065c9d…c394
2 touches
0 conflicts
0xbad6465e…42b8
0x065c9d…c394
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 0x87614c8ed1…84bbd9
Audit this contract →
← previous block·next block →recent activity