pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,263,379
17 transactions · 14 stateful · 2026-05-08 14:56:50 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,263,379 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e24c5e6…330d
0x754704…b603
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0x9dc9fa5f…7f23
0x34b655…2a6f
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0xe4b00f4b…34c0
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x3e1523…94aa
2 touches
0 conflicts
0x00000000…0001
0x3e1523…94aa
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: 0x754704bc…afb603
6 conflicts on slot 0x5e24c5e63c…91330d
Audit this contract →
← previous block·next block →recent activity