← previous blocknext block →recent activity
Analyzing
Block #73,744,026
16 transactions · 14 stateful · 2026-05-10 20:25:35 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,744,026 · 16 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
1w02w112w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0x4374760d…d8cb
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7aa41e40…35cb
0x065c9d…c394
2 touches
0 conflicts
0xa81f94fb…8383
0x065c9d…c394
2 touches
0 conflicts
0xe4c30421…048a
0x065c9d…c394
2 touches
0 conflicts
0xc3006de0…9726
0x188d58…ea8e
2 touches
0 conflicts
0xc3006de0…9728
0x188d58…ea8e
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 0x97d5efed7f…b81aa4
Audit this contract →
← previous block·next block →recent activity