← previous blocknext block →recent activity
Analyzing
Block #75,268,856
19 transactions · 16 stateful · 2026-05-17 22:03:35 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,268,856 · 19 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
1w02w14w05w19w010w115w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0xb1456a21…d57d
0x34b655…2a6f
6 touches
3 conflicts
0xc9ae4858…6c68
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity