pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,637,937
← previous block
next block →
recent activity
Analyzing
Block #82,637,937
10 transactions · 8 stateful · 2026-06-21 01:17:38 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,637,937
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
forward
#7
0x0f6795d9
#8
0x0f6795d9
#9
setData
#2
0x39ecce49
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x00000000…0002
0x019883…2a9a
4 touches
1 conflict
0x00000000…0003
0x019883…2a9a
4 touches
1 conflict
0xa10c86f8…4b74
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x019883…2a9a
4 touches
1 conflict
0xff1435f6…342f
0x0cc9b2…7777
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
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:
MONI (MONI)
1 conflict on slot
0x99a3a7c17c…081e2b
Audit this contract →
← previous block
·
next block →
recent activity