← previous blocknext block →recent activity
Analyzing
Block #75,702,905
22 transactions · 19 stateful · 2026-05-19 22:30:04 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,702,905 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w39w410w512w115w216w317w420w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x4d0e3f2f…3696
0x34b655…2a6f
4 touches
1 conflict
0x50059a18…9b7b
0x34b655…2a6f
4 touches
1 conflict
0x61128a54…c530
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity