← previous blocknext block →recent activity
Analyzing
Block #74,632,911
8 transactions · 6 stateful · 2026-05-14 23:16:43 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,632,911 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d82247b…e2dc
0x065c9d…c394
4 touches
1 conflict
0x59a992b4…3a62
0x065c9d…c394
4 touches
1 conflict
0x6db78287…5da8
0x065c9d…c394
3 touches
1 conflict
0x4b2ab58b…5ff0
0x065c9d…c394
3 touches
1 conflict
0xe8735a84…9d0f
0x065c9d…c394
3 touches
1 conflict
0x41861619…acbf
0x065c9d…c394
3 touches
1 conflict
0xc4cb5fb2…6a56
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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 0x5d82247b4c…b4e2dc
Audit this contract →
← previous block·next block →recent activity