← previous blocknext block →recent activity
Analyzing
Block #75,847,071
19 transactions · 17 stateful · 2026-05-20 14:31:03 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,847,071 · 19 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
2w03w14w25w310w011w116w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
12 touches
15 conflicts
0x908d4442…2c4b
0x34b655…2a6f
10 touches
10 conflicts
0x23ec8cdf…ef19
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x0711ec2d…d973
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x99f080dc…58c1
0x34b655…2a6f
8 touches
6 conflicts
0xd49762c9…1359
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity