pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,409,873
← previous block
next block →
recent activity
Analyzing
Block #81,409,873
8 transactions · 7 stateful · 2026-06-15 08:45:48 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,409,873
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
· blocks 1
#3
swap
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0xc7e3ec2c
#2
0x5bf9264c
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x49d58ea9…77eb
0x851145…3f07
4 touches
1 conflict
0xea163410…0281
0x851145…3f07
3 touches
1 conflict
0x022ae86a…3125
0x01bff4…1071
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x2ed341f1…bc57
0x01bff4…1071
2 touches
0 conflicts
0x3b2b747e…8e73
0x01bff4…1071
2 touches
0 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
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
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity