pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,098,040
← previous block
next block →
recent activity
Analyzing
Block #75,098,040
24 transactions · 14 stateful · 2026-05-17 03:02:40 UTC
Parallelism
88
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,098,040
· 24 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
0x1094dc9f
#4
exactOutputSingle
#5
exactOutputSingle
#6
execute
#7
0x5bf9264c
#8
0x5bf9264c
#9
0x1a945f9c
#10
forward
#11
updateDataFeedsValuesPartial
#12
0x5339c59f
#13
0x08e1a3…7dfc
#14
0x825dd2…01f7
#15
setData
#16
0x655fdf…f9cc
#17
0x6cd954…e5d2
#18
0x7c763c…8765
#19
0xf19584…5261
#20
0x007901…8844
#21
0x39435dac
· blocks 2
#22
0x39435dac
· blocks 1
#23
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
21
w0
22
w1
23
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
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21bf
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:
0x34b6552d…112a6f
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity