← previous blocknext block →recent activity
Analyzing
Block #75,513,108
22 transactions · 15 stateful · 2026-05-19 01:22:24 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,513,108 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w110w211w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54a1f6f…18f2
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xa7c45762…dc01
0x34b655…2a6f
8 touches
6 conflicts
0xd434422b…e717
0x34b655…2a6f
6 touches
3 conflicts
0x0175b1f6…af86
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x10f5f4d8…572e
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
6 conflicts on slot 0xe54a1f6fdd…7918f2
Audit this contract →
← previous block·next block →recent activity