Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c243490eb27ba6696a6263589dc2d915afb59de2388b6ae86338705b9fbdcdce

Tx prefix hash: 071b27548a58377a99f5192a8e324467cd3c55c21328f313da2f9e7627a74f7e
Tx public key: 4994e863b65bbac0e797011a2c6e9d413cf570c54aab05975d52f0f802ee98be
Timestamp: 1727447110 Timestamp [UCT]: 2024-09-27 14:25:10 Age [y:d:h:m:s]: 00:203:04:14:37
Block: 1119291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145035 RingCT/type: yes/0
Extra: 014994e863b65bbac0e797011a2c6e9d413cf570c54aab05975d52f0f802ee98be02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d1722e8af123286cb48c6b900904a48f4b297b97c306c3aec2693ef5e909ba2 0.600000000000 1600796 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": 1119301, "vin": [ { "gen": { "height": 1119291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d1722e8af123286cb48c6b900904a48f4b297b97c306c3aec2693ef5e909ba2" } } ], "extra": [ 1, 73, 148, 232, 99, 182, 91, 186, 192, 231, 151, 1, 26, 44, 110, 157, 65, 60, 245, 112, 197, 74, 171, 5, 151, 93, 82, 240, 248, 2, 238, 152, 190, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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