← previous blocknext block →recent activity
Analyzing
Block #73,687,819
16 transactions · 15 stateful · 2026-05-10 14:06:21 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,687,819 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x0ac31945…2c72
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x1c5f3087…d627
0x065c9d…c394
4 touches
1 conflict
0x731273dd…f703
0x065c9d…c394
3 touches
1 conflict
0x15652b2f…0889
0x065c9d…c394
3 touches
1 conflict
0x174a6457…83f1
0x065c9d…c394
3 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
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity