← previous blocknext block →recent activity
Analyzing
Block #75,893,387
23 transactions · 18 stateful · 2026-05-20 19:40:07 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,893,387 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w211w013w116w017w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7982ca1b…f8da
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0a809ce1…7894
0x34b655…2a6f
6 touches
3 conflicts
0x10814d14…cdda
0x34b655…2a6f
4 touches
1 conflict
0x111ac4b6…bcb9
0x34b655…2a6f
4 touches
1 conflict
0x1f01b15f…a050
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity