pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,037,373
14 transactions · 12 stateful · 2026-04-28 07:41:38 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,037,373 · 14 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
7w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xbf2fc8f6…85d2
0x065c9d…c394
3 touches
1 conflict
0xe22aad9a…aa01
0x065c9d…c394
3 touches
1 conflict
0x17a5f99d…d30b
0x065c9d…c394
3 touches
1 conflict
0x715670b8…788b
0x065c9d…c394
3 touches
1 conflict
0x81ba238f…5fb4
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: 0x065c9d28…a9c394
1 conflict on slot 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity