Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d816699426944d87e4c9b4778a5e8df2a8cf9a74054c10096dfbceb099540116

Tx prefix hash: 5ecca98e5d5d766c92f3e7dd26cb12b83a6732523c1fbc9d4ffc25738d29a7d4
Tx public key: 41148e81d12bc381141337f1b53270c925e9eb00ee8f0c2beb3bb2fd78fb0d05
Timestamp: 1719423646 Timestamp [UCT]: 2024-06-26 17:40:46 Age [y:d:h:m:s]: 01:134:01:14:47
Block: 1052770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354352 RingCT/type: yes/0
Extra: 0141148e81d12bc381141337f1b53270c925e9eb00ee8f0c2beb3bb2fd78fb0d050211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e233926c3a28765cb1bc6ab43518841b140c73dc9f80fe49649e8f6df62c9448 0.600000000000 1523103 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": 1052780, "vin": [ { "gen": { "height": 1052770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e233926c3a28765cb1bc6ab43518841b140c73dc9f80fe49649e8f6df62c9448" } } ], "extra": [ 1, 65, 20, 142, 129, 209, 43, 195, 129, 20, 19, 55, 241, 181, 50, 112, 201, 37, 233, 235, 0, 238, 143, 12, 43, 235, 59, 178, 253, 120, 251, 13, 5, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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