pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,354,733
← previous block
next block →
recent activity
Analyzing
Block #87,354,733
7 transactions · 6 stateful · 2026-07-12 21:59:22 UTC
Parallelism
43
/100
Blocked
50
%
Avg conflicts / tx
0.86
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,354,733
· 7 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0f6795d9
· blocks 3
#3
updateDataFeedsValuesPartial
#4
setData
#2
0x0f6795d9
· blocks 2
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0b26b03e…ecb6
0x34b655…2a6f
4 touches
1 conflict
0x1509d2c8…8461
0x34b655…2a6f
4 touches
1 conflict
0x217dce8d…7e14
0x34b655…2a6f
4 touches
1 conflict
0x372a3bdb…45f4
0x34b655…2a6f
4 touches
1 conflict
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
0x76e85a07…5ff1
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity