← previous blocknext block →recent activity
Analyzing
Block #75,734,235
18 transactions · 13 stateful · 2026-05-20 01:58:46 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,734,235 · 18 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
2w03w06w17w110w113w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac33ff75…077b
0xfa32f9…f3f0
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x3d34f2bd…5d63
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0xb5f01765…9b35
0x34b655…2a6f
4 touches
1 conflict
0xb7b446d2…2006
0x34b655…2a6f
4 touches
1 conflict
0xc108f63d…204f
0x34b655…2a6f
4 touches
1 conflict
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: 0xfa32f9ec…fef3f0
1 conflict on slot 0xac33ff75c1…89077b
Audit this contract →
← previous block·next block →recent activity