← previous blocknext block →recent activity
Analyzing
Block #74,254,980
7 transactions · 6 stateful · 2026-05-13 05:13:55 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,254,980 · 7 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f852347…2375
0x065c9d…c394
4 touches
1 conflict
0xcfb5de8d…f956
0x065c9d…c394
3 touches
1 conflict
0x63234b86…5b6c
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5c4e99f7…ab8e
0x065c9d…c394
2 touches
0 conflicts
0xb618965d…d430
0x065c9d…c394
2 touches
0 conflicts
0xcb15bf17…17dc
0x065c9d…c394
2 touches
0 conflicts
0x2e2214a9…fe0d
0x5d823e…89c6
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 0x9f8523472b…492375
Audit this contract →
← previous block·next block →recent activity