← previous blocknext block →recent activity
Analyzing
Block #73,674,205
20 transactions · 17 stateful · 2026-05-10 12:34:27 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,674,205 · 20 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
1w02w14w05w06w17w211w112w013w014w116w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x12f83d34…c2fa
0xd32edf…ff58
5 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x866bf367…7a60
0x188d58…ea8e
4 touches
1 conflict
0x866bf367…7a62
0x188d58…ea8e
4 touches
1 conflict
0x38aa1898…fdf5
0x1b6862…e19c
4 touches
1 conflict
0xb02fe354…948e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0000
0x1f86a9…17ed
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity