← previous blocknext block →recent activity
Analyzing
Block #73,663,754
20 transactions · 17 stateful · 2026-05-10 11:23:51 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,663,754 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w211w013w114w116w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38524fae…9deb
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf7c5003c…8dc0
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x9c7efe24…3d4b
0x34b655…2a6f
6 touches
3 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
6 touches
3 conflicts
0x5f450515…3bc4
0x34b655…2a6f
4 touches
1 conflict
0xe344d062…1602
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 0x38524faed4…ae9deb
Audit this contract →
← previous block·next block →recent activity