← previous blocknext block →recent activity
Analyzing
Block #75,622,394
40 transactions · 32 stateful · 2026-05-19 13:33:36 UTC
Parallelism
80/100
Blocked
69%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,622,394 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w18w210w213w314w315w416w517w018w119w221w022w123w224w329w230w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xd8c184f3…1811
0x34b655…2a6f
8 touches
6 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
6 touches
3 conflicts
0x37916bd8…7247
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0x87ae3334…a324
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity