← previous blocknext block →recent activity
Analyzing
Block #75,839,644
21 transactions · 17 stateful · 2026-05-20 13:41:06 UTC
Parallelism
81/100
Blocked
24%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,839,644 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0xd49762c9…1359
0x34b655…2a6f
8 touches
6 conflicts
0xf1b99c49…21d2
0x34b655…2a6f
6 touches
3 conflicts
0x0711ec2d…d973
0x34b655…2a6f
6 touches
3 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0xd0ec60a1…d247
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity