← previous blocknext block →recent activity
Analyzing
Block #73,014,811
10 transactions · 9 stateful · 2026-05-07 11:23:07 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,014,811 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47c1a8e8…f74a
0x34b655…2a6f
4 touches
1 conflict
0xdaca243a…f9de
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x4aed6ca6…cb48
0x065c9d…c394
3 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x14a37047…b17e
0x065c9d…c394
2 touches
0 conflicts
0x30bd0d85…d500
0x065c9d…c394
2 touches
0 conflicts
0x80e83c58…945b
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: Perpl
1 conflict on slot 0x47c1a8e802…12f74a
Audit this contract →
← previous block·next block →recent activity