← previous blocknext block →recent activity
Analyzing
Block #75,468,889
25 transactions · 17 stateful · 2026-05-18 20:21:00 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,468,889 · 25 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
1w02w13w04w15w06w17w18w214w015w116w223w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0xc3e09c17…7fdd
0xd32edf…ff58
5 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xaa7a2fe5…1178
0x34b655…2a6f
4 touches
1 conflict
0xd32f8498…be67
0x34b655…2a6f
4 touches
1 conflict
0xe1e41849…9772
0x34b655…2a6f
4 touches
1 conflict
0xfb6e6e75…02b1
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 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity