pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,091,763
11 transactions · 7 stateful · 2026-05-17 02:20:56 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,091,763 · 11 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
1w02w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xd030c62f…e167
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11a3c8c7…c46f
0x065c9d…c394
2 touches
0 conflicts
0x4697a512…462b
0x065c9d…c394
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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: 0x065c9d28…a9c394
1 conflict on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity