← previous blocknext block →recent activity
Analyzing
Block #74,519,625
10 transactions · 7 stateful · 2026-05-14 10:36:22 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,519,625 · 10 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
0x78b53e9b…0fea
0x065c9d…c394
4 touches
1 conflict
0xd9d83210…b1ff
0x065c9d…c394
4 touches
1 conflict
0x6c4026e9…67d9
0x065c9d…c394
3 touches
1 conflict
0x2b7451ea…aac0
0x065c9d…c394
3 touches
1 conflict
0x136b0f6d…fa83
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0xfd2febb9…7434
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 0x78b53e9b3f…f20fea
Audit this contract →
← previous block·next block →recent activity