← previous blocknext block →recent activity
Analyzing
Block #74,587,078
11 transactions · 10 stateful · 2026-05-14 18:10:23 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,587,078 · 11 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7abf1904…b003
0x065c9d…c394
3 touches
1 conflict
0xd82e22be…e8a4
0x065c9d…c394
3 touches
1 conflict
0x0a4aee6d…fc60
0x065c9d…c394
2 touches
0 conflicts
0x23e11a62…5906
0x065c9d…c394
2 touches
0 conflicts
0x80541caa…38e1
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity