Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a17239d1104678b8b0ed2ff11774eda5e7831bb0a24f47bc53b5fa78e93073b6

Tx prefix hash: b81b094b218ff5a53826c65d0902a7179944d90604c6dd97ad54dd6d3a039c10
Tx public key: 65e0e993d7c572c4efeaf5d0af15aeffad84e452f87f37b713154a51c163060e
Timestamp: 1739197179 Timestamp [UTC]: 2025-02-10 14:19:39 Age [y:d:h:m:s]: 01:093:11:03:20
Block: 1216269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317736 RingCT/type: yes/0
Extra: 0165e0e993d7c572c4efeaf5d0af15aeffad84e452f87f37b713154a51c163060e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd4b535470a169648544c3344043121b56dcb01d5be25841456b558b61bdca66 0.000600000000 1703074 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1216279, "vin": [ { "gen": { "height": 1216269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd4b535470a169648544c3344043121b56dcb01d5be25841456b558b61bdca66" } } ], "extra": [ 1, 101, 224, 233, 147, 215, 197, 114, 196, 239, 234, 245, 208, 175, 21, 174, 255, 173, 132, 228, 82, 248, 127, 55, 183, 19, 21, 74, 81, 193, 99, 6, 14, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: