← previous blocknext block →recent activity
Analyzing
Block #75,864,607
21 transactions · 19 stateful · 2026-05-20 16:28:32 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,864,607 · 21 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
2w03w14w25w06w17w28w310w012w113w018w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x3484c9df…bfd5
0x1d1325…2305
4 touches
1 conflict
0x8cf3d245…1d0d
0x1d1325…2305
4 touches
1 conflict
0xdb067026…9eb8
0x1d1325…2305
4 touches
1 conflict
0xe2e94dfa…5026
0x2a68ba…90c5
4 touches
1 conflict
0x20ac0567…c954
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity