← previous blocknext block →recent activity
Analyzing
Block #73,273,305
15 transactions · 13 stateful · 2026-05-08 16:02:58 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,273,305 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xf6993322…70ed
0x065c9d…c394
3 touches
1 conflict
0xcab2efd8…4cfc
0xd32edf…ff58
3 touches
1 conflict
0x7cc3a23d…4225
0x065c9d…c394
2 touches
0 conflicts
0x9842e76d…06bb
0x065c9d…c394
2 touches
0 conflicts
0x99c79b47…d79b
0x065c9d…c394
2 touches
0 conflicts
0xe19d0ee4…bffb
0x065c9d…c394
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity