pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,796,741
← previous block
next block →
recent activity
Analyzing
Block #86,796,741
12 transactions · 8 stateful · 2026-07-10 07:48:53 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,796,741
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
transfer
#8
setData
· blocks 1
#10
0xd3eccc…75b7
#11
0xf7e601…5feb
#9
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
2 touches
0 conflicts
0x35d95fb0…db9e
0x34b655…2a6f
2 touches
0 conflicts
0x35d95fb0…db9f
0x34b655…2a6f
2 touches
0 conflicts
0x393f6a3e…7288
0x34b655…2a6f
2 touches
0 conflicts
0x447c249a…b42c
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity