pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,275,822
← previous block
next block →
recent activity
Analyzing
Block #85,275,822
12 transactions · 10 stateful · 2026-07-03 06:39:32 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,275,822
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x719d975a
#4
0x05ee6a22
#5
0xab083028
#7
updateDataFeedsValuesPartial
#8
0x5a5d9a99
#9
0xed82b078
#10
setData
#11
0x39435dac
#2
0x0c7abd22
#6
0x13572d0b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xe15320…7f44
4 touches
1 conflict
0xad436b12…f632
0x1111b3…4111
4 touches
1 conflict
0xb7fefa89…54dc
0x754704…b603
4 touches
1 conflict
0xe782fcdb…edef
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x87cb50…0e86
4 touches
1 conflict
0x00000000…0003
0x87cb50…0e86
4 touches
1 conflict
0x00000000…0004
0x87cb50…0e86
4 touches
1 conflict
0x3833c9c9…14dd
0x1111b3…4111
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:
0xe153201e…c97f44
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity