Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0183a5bde061332dbc00e09ab8ea9aa8f199cf1e611b6cbb89c390ff2c61d3b

Tx prefix hash: 59f082ef83f72d56896f4a9efd6871465412c277d3463a83e266eaec452c838f
Tx public key: 816953787c5204963de6e6dbac84227d8748c74fd442825d15d5ae50eb686d3d
Timestamp: 1736448464 Timestamp [UCT]: 2025-01-09 18:47:44 Age [y:d:h:m:s]: 00:103:10:40:09
Block: 1193780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73715 RingCT/type: yes/0
Extra: 01816953787c5204963de6e6dbac84227d8748c74fd442825d15d5ae50eb686d3d0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7ae6c0343ccd0c50f3dccd5f4c2f2d63b43a7eacd826d09439c6842611c7577 0.600000000000 1680345 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": 1193790, "vin": [ { "gen": { "height": 1193780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7ae6c0343ccd0c50f3dccd5f4c2f2d63b43a7eacd826d09439c6842611c7577" } } ], "extra": [ 1, 129, 105, 83, 120, 124, 82, 4, 150, 61, 230, 230, 219, 172, 132, 34, 125, 135, 72, 199, 79, 212, 66, 130, 93, 21, 213, 174, 80, 235, 104, 109, 61, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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