pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,493,072
← previous block
next block →
recent activity
Analyzing
Block #83,493,072
9 transactions · 7 stateful · 2026-06-25 00:32:42 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,493,072
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x13572d0b
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#6
0x6a3c77a2
#7
0x6a3c77a2
#8
setData
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3833c9c9…14dd
0x1111b3…4111
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0xb7fefa89…54dc
0x754704…b603
2 touches
0 conflicts
0xd9403e43…b6ac
0x754704…b603
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
0xe99d8e683a…2ea16e
Audit this contract →
← previous block
·
next block →
recent activity