← previous blocknext block →recent activity
Analyzing
Block #74,231,920
19 transactions · 17 stateful · 2026-05-13 02:40:37 UTC
Parallelism
58/100
Blocked
59%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,231,920 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w010w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xa092ff7d…bd83
0x065c9d…c394
4 touches
1 conflict
0xa90e2bb7…2758
0x065c9d…c394
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x44ad89ba…cf83
0x0cc9b2…7777
4 touches
1 conflict
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
15 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity