← previous blocknext block →recent activity
Analyzing
Block #74,594,636
20 transactions · 12 stateful · 2026-05-14 19:00:57 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,594,636 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w29w310w011w112w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0x0bebbbc2…2c5b
0xd32edf…ff58
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x2ff60060…0e2e
0x065c9d…c394
3 touches
1 conflict
0x741c047a…fe85
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity