← previous blocknext block →recent activity
Analyzing
Block #75,617,556
13 transactions · 10 stateful · 2026-05-19 13:01:05 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,617,556 · 13 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
1w02w06w18w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0xbdb4cdf8…0e0b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa1d44989…07f0
0x065c9d…c394
3 touches
1 conflict
0xf847c44b…e82a
0x065c9d…c394
3 touches
1 conflict
0x9bf064a6…4f04
0x2a68ba…90c5
2 touches
0 conflicts
0x080970fe…1375
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 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity