← previous blocknext block →recent activity
Analyzing
Block #75,066,711
8 transactions · 7 stateful · 2026-05-16 23:33:22 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,066,711 · 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46a1bf16…f563
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0x199ef691…6688
0x2ae0cf…3d4e
2 touches
0 conflicts
0x754fac2d…b3aa
0x2ae0cf…3d4e
2 touches
0 conflicts
0x84a19d57…05af
0x2ae0cf…3d4e
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 0x46a1bf1694…a6f563
Audit this contract →
← previous block·next block →recent activity