pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,314,463
← previous block
next block →
recent activity
Analyzing
Block #74,314,463
10 transactions · 7 stateful · 2026-05-13 11:49:34 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,314,463
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6df9e92b
· blocks 1
#4
0x5339c59f
#5
0x5339c59f
#6
setData
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#3
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73131ffc…b46c
0x5df178…7777
4 touches
1 conflict
0x00000000…0000
0x2c492d…444e
4 touches
1 conflict
0x00000000…0001
0x2c492d…444e
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xc740dd24…9801
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x5df178…7777
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x4ec9ff52…e6f7
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:
0x5df178c7…167777
1 conflict on slot
0x73131ffcb8…24b46c
Audit this contract →
← previous block
·
next block →
recent activity