← previous blocknext block →recent activity
Analyzing
Block #74,255,550
7 transactions · 6 stateful · 2026-05-13 05:17:43 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,255,550 · 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
0xf7b57fa1…468a
0x065c9d…c394
3 touches
1 conflict
0x84a0f21c…0254
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x25fd8762…ce5d
0x065c9d…c394
2 touches
0 conflicts
0x4d28b007…c181
0x065c9d…c394
2 touches
0 conflicts
0x604078cc…1e37
0x065c9d…c394
2 touches
0 conflicts
0x791ffa17…2a9d
0x065c9d…c394
2 touches
0 conflicts
0xb78cc6db…0cf4
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
1 conflict on slot 0xf7b57fa197…95468a
Audit this contract →
← previous block·next block →recent activity