← previous blocknext block →recent activity
Analyzing
Block #75,523,282
16 transactions · 7 stateful · 2026-05-19 02:31:58 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,523,282 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0fb63d98…7d4c
0xd32edf…ff58
3 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x309ef367…e8a1
0x34b655…2a6f
2 touches
0 conflicts
0x399d330d…da84
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe5e7089a63…bcfb91
Audit this contract →
← previous block·next block →recent activity