← previous blocknext block →recent activity
Analyzing
Block #73,214,225
37 transactions · 27 stateful · 2026-05-08 09:29:55 UTC
Parallelism
86/100
Blocked
52%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,214,225 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w08w19w010w111w212w313w414w430w132w233w334w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x542861e4…e24a
0xd32edf…ff58
9 touches
10 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x2c76dc38…4a52
0x065c9d…c394
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity