← previous blocknext block →recent activity
Analyzing
Block #75,987,079
10 transactions · 7 stateful · 2026-05-21 06:03:52 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,987,079 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x699e5877…05ab
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x138aa8a0…71d6
0x34b655…2a6f
2 touches
0 conflicts
0x15569666…5aca
0x34b655…2a6f
2 touches
0 conflicts
0x22152b6e…8590
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x3b6a2d31…4747
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
3 conflicts on slot 0x699e587700…aa05ab
Audit this contract →
← previous block·next block →recent activity