← previous blocknext block →recent activity
Analyzing
Block #74,413,912
14 transactions · 13 stateful · 2026-05-13 22:51:18 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,413,912 · 14 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
1w05w16w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc998adb0…35d7
0x065c9d…c394
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x667fcadb…4835
0x065c9d…c394
3 touches
1 conflict
0xb0e30944…e444
0x065c9d…c394
3 touches
1 conflict
0x841ce5a4…5d00
0x065c9d…c394
2 touches
0 conflicts
0xa37d962b…c55b
0x065c9d…c394
2 touches
0 conflicts
0x1c389468…6b0e
0x34b655…2a6f
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 0xc998adb091…8c35d7
Audit this contract →
← previous block·next block →recent activity