← previous blocknext block →recent activity
Analyzing
Block #75,262,435
8 transactions · 6 stateful · 2026-05-17 21:20:32 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,262,435 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba9f88e8…9c33
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x18b11fba…c92a
0x34b655…2a6f
4 touches
1 conflict
0x60a42a5e…9da2
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b77
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
2 touches
0 conflicts
0x71e4ffd1…9beb
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 0xba9f88e88a…879c33
Audit this contract →
← previous block·next block →recent activity