← previous blocknext block →recent activity
Analyzing
Block #73,674,395
28 transactions · 21 stateful · 2026-05-10 12:35:44 UTC
Parallelism
82/100
Blocked
67%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,674,395 · 28 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
1w02w13w25w06w07w18w210w311w213w014w115w216w317w418w219w322w025w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…0001
0x659bd0…a9da
6 touches
3 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
6 touches
3 conflicts
0x7e28e55c…d05c
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0x659bd0…a9da
6 touches
3 conflicts
0x406e2fb1…f06b
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity