← previous blocknext block →recent activity
Analyzing
Block #75,845,785
30 transactions · 21 stateful · 2026-05-20 14:22:25 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,845,785 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w412w513w014w115w220w621w627w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
10 touches
10 conflicts
0xcc400974…966d
0xd32edf…ff58
9 touches
10 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0x451e482b59…427e7d
Audit this contract →
← previous block·next block →recent activity