← previous blocknext block →recent activity
Analyzing
Block #74,937,990
12 transactions · 10 stateful · 2026-05-16 09:12:47 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,937,990 · 12 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
1w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ba75d8…354e
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x21fa526f…04a3
0x065c9d…c394
3 touches
1 conflict
0x39b63a05…920e
0x065c9d…c394
3 touches
1 conflict
0x2232fa7e…2305
0x065c9d…c394
2 touches
0 conflicts
0x23182fb5…ad57
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x5204335e…3581
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 0x53ba75d8f8…4d354e
Audit this contract →
← previous block·next block →recent activity