← previous blocknext block →recent activity
Analyzing
Block #75,336,666
8 transactions · 7 stateful · 2026-05-18 05:37:24 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,336,666 · 8 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b16dd0…0426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x10814d14…cdda
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x310a7246…2dcb
0x34b655…2a6f
2 touches
0 conflicts
0x331141f3…be83
0x34b655…2a6f
2 touches
0 conflicts
0x5648d337…a780
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 0xb7b16dd022…c80426
Audit this contract →
← previous block·next block →recent activity