pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,688,902
10 transactions · 10 stateful · 2026-05-10 14:13:40 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,688,902 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xbc85747a…a1c0
0x065c9d…c394
3 touches
1 conflict
0x1aba5fe2…62f4
0x065c9d…c394
3 touches
1 conflict
0x0d2556e0…a96c
0x065c9d…c394
2 touches
0 conflicts
0x56480508…ac9c
0x065c9d…c394
2 touches
0 conflicts
0xae69c125…2379
0x2a68ba…90c5
2 touches
0 conflicts
0xc9e97522…3519
0x2a68ba…90c5
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: 0x065c9d28…a9c394
3 conflicts on slot 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity