← previous blocknext block →recent activity
Analyzing
Block #74,771,267
19 transactions · 8 stateful · 2026-05-15 14:40:34 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,771,267 · 19 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
2w03w15w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19df127f…e997
0x065c9d…c394
4 touches
1 conflict
0xd8bfa141…3571
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xc9cc7727…5625
0x065c9d…c394
3 touches
1 conflict
0xaab6a37f…eb40
0x065c9d…c394
3 touches
1 conflict
0x54bf0354…7f1b
0x065c9d…c394
3 touches
1 conflict
0x5f8e94aa…565f
0x065c9d…c394
3 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
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 0x19df127fcd…38e997
Audit this contract →
← previous block·next block →recent activity