← previous blocknext block →recent activity
Analyzing
Block #75,507,213
10 transactions · 10 stateful · 2026-05-19 00:42:00 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,507,213 · 10 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9fe7
0x16f70c…c3dd
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity