← previous blocknext block →recent activity
Analyzing
Block #73,571,810
14 transactions · 13 stateful · 2026-05-10 01:08:30 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,571,810 · 14 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
1w06w07w08w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x462c8be7…4f83
0x8d66a4…3095
4 touches
1 conflict
0x0bf146e8…f5c1
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x363f6fe8…9870
0x065c9d…c394
3 touches
1 conflict
0x5fc20e09…0ee7
0x065c9d…c394
3 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: 0x8d66a43f…113095
1 conflict on slot 0x8a35acfbc1…6bd1ab
Audit this contract →
← previous block·next block →recent activity