← previous blocknext block →recent activity
Analyzing
Block #75,686,730
10 transactions · 6 stateful · 2026-05-19 20:42:43 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,686,730 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f84702c…c5f9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0a3cb2fb…2a14
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x48e4e1cf…f91b
0x34b655…2a6f
2 touches
0 conflicts
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x8f84702c8c…58c5f9
Audit this contract →
← previous block·next block →recent activity