← previous blocknext block →recent activity
Analyzing
Block #75,730,620
17 transactions · 13 stateful · 2026-05-20 01:34:41 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,730,620 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w210w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x422d5490…52d9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x98e0e85c…c45a
0x34b655…2a6f
4 touches
1 conflict
0xb5f5f775…010b
0x34b655…2a6f
4 touches
1 conflict
0xbc04d98e…a484
0x34b655…2a6f
4 touches
1 conflict
0xc166a323…1f33
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 0x422d549061…1f52d9
Audit this contract →
← previous block·next block →recent activity