← previous blocknext block →recent activity
Analyzing
Block #73,496,377
13 transactions · 10 stateful · 2026-05-09 16:47:14 UTC
Parallelism
46/100
Blocked
70%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,496,377 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w16w27w38w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x803ba8bc…0c5d
0x065c9d…c394
4 touches
1 conflict
0xa6fd78ef…c615
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity