← previous blocknext block →recent activity
Analyzing
Block #75,128,036
16 transactions · 14 stateful · 2026-05-17 06:22:52 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,128,036 · 16 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
1w03w04w15w28w39w113w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x908d4442…2c4b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0380ead4…3a27
0x34b655…2a6f
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
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
3 conflicts on slot 0x908d4442aa…222c4b
Audit this contract →
← previous block·next block →recent activity