pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,096,495
12 transactions · 8 stateful · 2026-05-17 02:52:21 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,096,495 · 12 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
1w02w15w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69562b24…2ef8
0x5afd3e…7620
4 touches
1 conflict
0x94d9d0d7…6d5f
0x5afd3e…7620
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0xb6b4aae6…d834
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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: 0x5afd3ec8…e77620
1 conflict on slot 0x69562b243f…142ef8
Audit this contract →
← previous block·next block →recent activity