← previous blocknext block →recent activity
Analyzing
Block #73,808,731
16 transactions · 13 stateful · 2026-05-11 03:41:45 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,808,731 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w112w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8240d70c…7c3b
0x34b655…2a6f
8 touches
6 conflicts
0x42deeec2…4566
0x34b655…2a6f
4 touches
1 conflict
0x97266401…ed31
0x34b655…2a6f
4 touches
1 conflict
0xb81d3ee7…3947
0x34b655…2a6f
4 touches
1 conflict
0xd93ee5f0…5e71
0xd32edf…ff58
3 touches
1 conflict
0x6af306bb…2e81
0x3bd359…433a
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
2 touches
0 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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity