pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,199,038
← previous block
next block →
recent activity
Analyzing
Block #75,199,038
11 transactions · 8 stateful · 2026-05-17 14:16:57 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,199,038
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xce1e7030
#2
forward
#3
0xed82b078
#4
updateDataFeedsValuesPartial
#5
0x6a09ce50
#6
0x56174e…582e
#7
0x834f09…1ae8
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xded5ec0c…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x46a1bf16…f563
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x097d40…9920
2 touches
0 conflicts
0x00000000…0002
0x2d84d7…d457
2 touches
0 conflicts
0x00000000…0003
0x2d84d7…d457
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
0xded5ec0c97…40f0fc
Audit this contract →
← previous block
·
next block →
recent activity