← previous blocknext block →recent activity
Analyzing
Block #74,024,781
6 transactions · 6 stateful · 2026-05-12 03:42:45 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,024,781 · 6 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
2w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xb93a5822…d311
0x065c9d…c394
4 touches
1 conflict
0x340fa973…e4a6
0x065c9d…c394
3 touches
1 conflict
0x3f6c5271…01f4
0x065c9d…c394
2 touches
0 conflicts
0x998ef5ed…86fe
0x065c9d…c394
2 touches
0 conflicts
0xb8733398…55f8
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity