pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,328,213
← previous block
next block →
recent activity
Analyzing
Block #84,328,213
9 transactions · 9 stateful · 2026-06-28 21:20:26 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,328,213
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x5a5d9a99
#4
0x0f6795d9
· blocks 1
#6
0x85367786
· blocks 1
#8
0x6a419091
#5
0x0f6795d9
#7
0x85367786
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0016
0x8fbe07…71b6
4 touches
1 conflict
0x0494780e…2900
0x8fbe07…71b6
4 touches
1 conflict
0xa6fd7409…16b7
0x8fbe07…71b6
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0x5ebb19ec…ce9a
0xdde003…c9a4
4 touches
1 conflict
0xb983f9fc…9b91
0xdde003…c9a4
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:
0x8fbe0741…fa71b6
1 conflict on slot
0x0000000000…000016
Audit this contract →
← previous block
·
next block →
recent activity