← previous blocknext block →recent activity
Analyzing
Block #73,274,006
17 transactions · 17 stateful · 2026-05-08 16:07:38 UTC
Parallelism
35/100
Blocked
65%
Avg conflicts / tx
2.35
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,274,006 · 17 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
18 touches
36 conflicts
0xbdff944d…447e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8d0dfe2c…3345
0x2a68ba…90c5
4 touches
1 conflict
0xd821ae10…fe17
0xc8689a…ee79
4 touches
1 conflict
0xe84995e9…8dd2
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x45440ad0…6149
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: 0xab35264b…1cfa38
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity