← previous blocknext block →recent activity
Analyzing
Block #75,846,333
21 transactions · 19 stateful · 2026-05-20 14:26:07 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,846,333 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w27w18w111w012w114w215w217w218w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
6 touches
3 conflicts
0x705a9a1a…db08
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0x75c3ab…4f0d
4 touches
1 conflict
0x82b86244…b54a
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity