pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,675,872
← previous block
next block →
recent activity
Analyzing
Block #75,675,872
10 transactions · 9 stateful · 2026-05-19 19:30:33 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,675,872
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
multicall
#2
closeTrade
#3
forward
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
setData
#7
0x39435dac
· blocks 2
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x064a3cb8…c43e
0x09475a…400f
2 touches
0 conflicts
0x50b825f2…76d6
0x09475a…400f
2 touches
0 conflicts
0xd420023a…cf6a
0x09475a…400f
2 touches
0 conflicts
0x10633389…ed43
0xd18b7e…414b
2 touches
0 conflicts
0x5cdc8924…c0f1
0xd18b7e…414b
2 touches
0 conflicts
0x34e65d5c…838e
0xd5d960…eaee
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity