← previous blocknext block →recent activity
Analyzing
Block #73,706,594
13 transactions · 11 stateful · 2026-05-10 16:12:57 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,706,594 · 13 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
2w05w16w27w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x43fac642…d9c8
0x065c9d…c394
4 touches
1 conflict
0x19985c1e…6c42
0x065c9d…c394
3 touches
1 conflict
0xaa78e54c…cf11
0x065c9d…c394
3 touches
1 conflict
0x00000000…0036
0x386489…7508
2 touches
0 conflicts
0x4546ea5b…0eb8
0x386489…7508
2 touches
0 conflicts
0x15bae5fc…9f7e
0x57ea24…2cec
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 0x0ac3194537…8f2c72
Audit this contract →
← previous block·next block →recent activity