pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,090,362
16 transactions · 12 stateful · 2026-04-28 13:34:35 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,090,362 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w07w18w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b61282e…1ccd
0xd32edf…ff58
9 touches
10 conflicts
0x392a02b5…0019
0x81a224…7777
4 touches
1 conflict
0x4c770fe0…b972
0x3bd359…433a
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x00000000…0000
0x714a26…182d
4 touches
1 conflict
0x00000000…0001
0x714a26…182d
4 touches
1 conflict
0x00000000…0003
0x714a26…182d
4 touches
1 conflict
0x8be2a8b2…91f2
0x3bd359…433a
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: 0xd32edf66…9fff58
10 conflicts on slot 0x1b61282ef7…181ccd
Audit this contract →
← previous block·next block →recent activity