← previous blocknext block →recent activity
Analyzing
Block #74,460,393
19 transactions · 15 stateful · 2026-05-14 04:00:42 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,460,393 · 19 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
2w09w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x27108350…3412
0x065c9d…c394
2 touches
0 conflicts
0x27fd8c30…17c9
0x065c9d…c394
2 touches
0 conflicts
0x6dbeb988…8637
0x065c9d…c394
2 touches
0 conflicts
0xb6635423…a29d
0x065c9d…c394
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity