Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 685c2cd7a7e5fea2494d8e7431a85f05ff6a7fc0cf2e81b31709ce5f4209dca3

Tx prefix hash: a927eef70e7834e7766dfa3e971b412bda20ae50e6214e33d3035f7b346b579c
Tx public key: cc1eb8276e4ae03b280be6dcfafce83c7923958c0146d1cbcbf4491575c59498
Timestamp: 1744291774 Timestamp [UTC]: 2025-04-10 13:29:34 Age [y:d:h:m:s]: 01:217:10:21:05
Block: 1258447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419301 RingCT/type: yes/0
Extra: 01cc1eb8276e4ae03b280be6dcfafce83c7923958c0146d1cbcbf4491575c594980211000000032609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 633b1ee102329c18872ddbffc19c288fa56bb9ef6f0cbbb0c3338761f47f6a21 0.000600000000 1745580 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": 1258457, "vin": [ { "gen": { "height": 1258447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "633b1ee102329c18872ddbffc19c288fa56bb9ef6f0cbbb0c3338761f47f6a21" } } ], "extra": [ 1, 204, 30, 184, 39, 110, 74, 224, 59, 40, 11, 230, 220, 250, 252, 232, 60, 121, 35, 149, 140, 1, 70, 209, 203, 203, 244, 73, 21, 117, 197, 148, 152, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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: