← previous blocknext block →recent activity
Analyzing
Block #75,196,116
23 transactions · 21 stateful · 2026-05-17 13:57:24 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,196,116 · 23 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
1w02w13w212w015w016w119w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a672810…1732
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5d
0x188d58…ea8e
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 0x7a6728105c…191732
Audit this contract →
← previous block·next block →recent activity