← previous blocknext block →recent activity
Analyzing
Block #75,668,614
9 transactions · 8 stateful · 2026-05-19 18:42:10 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,668,614 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x50e10826…843b
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0xc009105d…96f7
0x8d66a4…3095
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
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
1 conflict on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity