← previous blocknext block →recent activity
Analyzing
Block #73,372,970
10 transactions · 9 stateful · 2026-05-09 03:06:03 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,372,970 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc5b80247…5c47
0x065c9d…c394
3 touches
1 conflict
0x00000000…0002
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x83a78bec…0901
0x059114…ac3b
2 touches
0 conflicts
0xa1928f4d…0f40
0x059114…ac3b
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 0x4d87512b00…43897c
Audit this contract →
← previous block·next block →recent activity