pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,214,246
11 transactions · 9 stateful · 2026-05-03 18:24:58 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,214,246 · 11 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
2w03w14w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6bfc4098…9e4c
0x065c9d…c394
2 touches
0 conflicts
0x80160b33…10e4
0x065c9d…c394
2 touches
0 conflicts
0xb9472036…dab0
0x065c9d…c394
2 touches
0 conflicts
0xcada175e…40a0
0x065c9d…c394
2 touches
0 conflicts
0xfe735f9a…c94a
0x065c9d…c394
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: 0x7e9d3a8a…4f9fda
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity