← previous blocknext block →recent activity
Analyzing
Block #75,892,653
9 transactions · 9 stateful · 2026-05-20 19:35:14 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,892,653 · 9 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
1w02w16w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1e6ad9ec…011e
0xd32edf…ff58
3 touches
1 conflict
0x062cbb5d…35d3
0x065c9d…c394
2 touches
0 conflicts
0x52c7f1a6…fca4
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x8d441e57…0306
0x065c9d…c394
2 touches
0 conflicts
0xa698ca2a…1ab4
0x065c9d…c394
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 0x206f43799d…55e08a
Audit this contract →
← previous block·next block →recent activity