← previous blocknext block →recent activity
Analyzing
Block #74,788,879
12 transactions · 11 stateful · 2026-05-15 16:38:15 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,788,879 · 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
1w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d4aab55…74ae
0x065c9d…c394
4 touches
1 conflict
0xe6f3ee49…2cdb
0x065c9d…c394
4 touches
1 conflict
0x39b9ce7d…c0f6
0x065c9d…c394
3 touches
1 conflict
0x9c64d845…0588
0x065c9d…c394
3 touches
1 conflict
0xcef57a96…2c88
0x065c9d…c394
3 touches
1 conflict
0x138e3f85…9271
0x065c9d…c394
3 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
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 0x6d4aab557e…7174ae
Audit this contract →
← previous block·next block →recent activity