← previous blocknext block →recent activity
Analyzing
Block #75,551,012
17 transactions · 11 stateful · 2026-05-19 05:36:46 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,551,012 · 17 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
1w02w13w29w313w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x070a562a…8147
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xe1e41849…9772
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f94ee4c…1898
0x1b6862…e19c
6 touches
3 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0x83caf80c…96fe
0xd32edf…ff58
5 touches
3 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
3 conflicts on slot 0x070a562acf…648147
Audit this contract →
← previous block·next block →recent activity