← previous blocknext block →recent activity
Analyzing
Block #74,442,188
8 transactions · 7 stateful · 2026-05-14 01:59:32 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,442,188 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x68b2601a…499f
0x065c9d…c394
2 touches
0 conflicts
0xa17ed895…671e
0x065c9d…c394
2 touches
0 conflicts
0xa68056a7…b799
0x065c9d…c394
2 touches
0 conflicts
0xb86cb8d9…73d0
0x065c9d…c394
2 touches
0 conflicts
0xca77bfc6…5b70
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity