← previous blocknext block →recent activity
Analyzing
Block #73,668,669
17 transactions · 16 stateful · 2026-05-10 11:57:04 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,668,669 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w29w010w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2438038…5fa7
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0eac6378…36f4
0x34b655…2a6f
8 touches
6 conflicts
0xd77e90ec…8c04
0x3bd359…433a
6 touches
3 conflicts
0x3e733ae4…4598
0x34b655…2a6f
6 touches
3 conflicts
0xe4da0681…b19d
0x34b655…2a6f
6 touches
3 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xf2438038b6…475fa7
Audit this contract →
← previous block·next block →recent activity