← previous blocknext block →recent activity
Analyzing
Block #73,663,790
25 transactions · 21 stateful · 2026-05-10 11:24:05 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,663,790 · 25 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
1w07w110w011w112w213w222w023w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7c5003c…8dc0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x23951077…539b
0x34b655…2a6f
4 touches
1 conflict
0x38524fae…9deb
0x34b655…2a6f
4 touches
1 conflict
0x57de3828…3fbb
0x34b655…2a6f
4 touches
1 conflict
0x6eba5e7f…4b52
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
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
3 conflicts on slot 0xf7c5003cc4…138dc0
Audit this contract →
← previous block·next block →recent activity