pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,621,017
← previous block
next block →
recent activity
Analyzing
Block #87,621,017
11 transactions · 9 stateful · 2026-07-14 03:41:00 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,621,017
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0x0f6795d9
· blocks 1
#8
setData
#9
0x287633…72bd
#10
0x785f5745
#3
0x98717539
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd19c9d38…b459
0x34b655…2a6f
4 touches
1 conflict
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x9040c7dc…eac5
0x34b655…2a6f
2 touches
0 conflicts
0x9407f89d…82ff
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
0xed59b1cd08…c98509
Audit this contract →
← previous block
·
next block →
recent activity