← previous blocknext block →recent activity
Analyzing
Block #75,990,306
8 transactions · 8 stateful · 2026-05-21 06:25:19 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,990,306 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f7781d6…e632
0x34b655…2a6f
4 touches
1 conflict
0x3b86caa0…a2a9
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x702a42fb…3d10
0x065c9d…c394
2 touches
0 conflicts
0x861237f9…e40a
0x065c9d…c394
2 touches
0 conflicts
0x8da19cbe…b5d9
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 0x2f7781d6c5…16e632
Audit this contract →
← previous block·next block →recent activity