pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,970,735
10 transactions · 9 stateful · 2026-05-11 21:40:29 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,970,735 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f0eb83e…6daf
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xf39e38d0…dd30
0x065c9d…c394
3 touches
1 conflict
0x512973f9…9731
0x065c9d…c394
3 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: 0xfd44b351…7f00d1
1 conflict on slot 0x9f0eb83e73…1d6daf
Audit this contract →
← previous block·next block →recent activity