← previous blocknext block →recent activity
Analyzing
Block #75,019,455
18 transactions · 16 stateful · 2026-05-16 18:18:40 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.22
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,019,455 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w19w013w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa2d82572…8766
0xd32edf…ff58
9 touches
10 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x014b941d…ccce
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
0x6d0c65d9…c36f
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xb96e29a5…0419
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity