← previous blocknext block →recent activity
Analyzing
Block #73,037,008
27 transactions · 22 stateful · 2026-05-07 13:50:50 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,037,008 · 27 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
1w02w13w24w35w48w39w010w111w212w318w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
16 touches
28 conflicts
0xce779f61…be1f
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 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: 0xd574cae5…037ab1
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity