pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,472,465
← previous block
next block →
recent activity
Analyzing
Block #75,472,465
9 transactions · 8 stateful · 2026-05-18 20:44:47 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,472,465
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
forward
#5
0x6a0b7ab7
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0xbb80bfed…80bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xded5ec0c…f0fc
0x34b655…2a6f
4 touches
1 conflict
0x1dd49448…8489
0x065c9d…c394
2 touches
0 conflicts
0x217d3916…708a
0x065c9d…c394
2 touches
0 conflicts
0x2bba936a…01cc
0x065c9d…c394
2 touches
0 conflicts
0x7936b3b3…f5d7
0x065c9d…c394
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
0x5086c64a56…bb28ba
Audit this contract →
← previous block
·
next block →
recent activity