pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,282,355
← previous block
next block →
recent activity
Analyzing
Block #85,282,355
10 transactions · 10 stateful · 2026-07-03 07:23:01 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,282,355
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x957d4ba0
· blocks 2
#4
0x39435dac
#5
0x0f6795d9
#6
0x3f5c179b
#7
0x0c7abd22
#8
forward
#9
setData
#2
0x957d4ba0
· blocks 1
#3
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x006e55b1…660f
0x8d1565…6723
6 touches
3 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x34443913…cbf3
0x336ed4…c59c
5 touches
3 conflicts
0x4a870d86…79ef
0x336ed4…c59c
4 touches
1 conflict
0x09f900fb…0573
0x34b655…2a6f
2 touches
0 conflicts
0x12573732…e891
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:
0x8d156514…236723
3 conflicts on slot
0x006e55b1f3…44660f
Audit this contract →
← previous block
·
next block →
recent activity