← previous blocknext block →recent activity
Analyzing
Block #73,808,790
16 transactions · 15 stateful · 2026-05-11 03:42:09 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,808,790 · 16 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
1w02w13w04w16w07w29w010w111w213w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8240d70c…7c3b
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe10af7c8…cae8
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x23114fac…630a
0x34b655…2a6f
4 touches
1 conflict
0x312c5cb2…7f25
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
6 conflicts on slot 0x8240d70c8a…f27c3b
Audit this contract →
← previous block·next block →recent activity