Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae12288458227e8f3c70b60f3b95bddc58e8eb5004f8a3412af0ee8bc8b6301e

Tx prefix hash: 99d182ed24f720c129a65b34c7125c3dcaba71d6244c35f8894abaf45cb230b5
Tx public key: 72dfe0671e509b50467a344fca95e5692c576d7a376ab3d7dbfb272a56f19de6
Timestamp: 1762406130 Timestamp [UCT]: 2025-11-06 05:15:30 Age [y:d:h:m:s]: 00:022:00:37:25
Block: 1405988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15784 RingCT/type: yes/0
Extra: 0172dfe0671e509b50467a344fca95e5692c576d7a376ab3d7dbfb272a56f19de6021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb460f3737da330beb636dcc863ea69e488c23e4eab241ace6d75dfa919a4bcf 0.600000000000 1894369 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 dinasty-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": 1405998, "vin": [ { "gen": { "height": 1405988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb460f3737da330beb636dcc863ea69e488c23e4eab241ace6d75dfa919a4bcf" } } ], "extra": [ 1, 114, 223, 224, 103, 30, 80, 155, 80, 70, 122, 52, 79, 202, 149, 229, 105, 44, 87, 109, 122, 55, 106, 179, 215, 219, 251, 39, 42, 86, 241, 157, 230, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8