pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,269,572
← previous block
next block →
recent activity
Analyzing
Block #75,269,572
13 transactions · 9 stateful · 2026-05-17 22:08:23 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,269,572
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0a3cce
#2
0xed82b078
#3
0x98717539
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
aggregate3
#7
0x6a0a3cce
#8
setData
#9
0x377b55…3e99
#10
0xddd90e…c356
#11
0x84a139…2819
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x70d3da25…080e
0x065c9d…c394
2 touches
0 conflicts
0x968bdacb…f461
0x2a68ba…90c5
2 touches
0 conflicts
0x0520da1d…c88e
0x34b655…2a6f
2 touches
0 conflicts
0x15ad1b43…10de
0x34b655…2a6f
2 touches
0 conflicts
0x34de6bae…7a7c
0x34b655…2a6f
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
0x801a6e5726…c1d85c
Audit this contract →
← previous block
·
next block →
recent activity