Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772e55ad9a9eb63f5aee0f2984c102a6d19e8b006d7f40b99a0915c14a7a1128

Tx prefix hash: e14d585e538a3cb253b8128c3d000b62842233ef4f712145b8b5fb1c8b569343
Tx public key: 6bc79eb650acaae6775908b59317e59cd467b5d30722f8366643e7e4d120ffb7
Timestamp: 1578793973 Timestamp [UCT]: 2020-01-12 01:52:53 Age [y:d:h:m:s]: 05:103:06:00:19
Block: 43570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1224007 RingCT/type: yes/0
Extra: 016bc79eb650acaae6775908b59317e59cd467b5d30722f8366643e7e4d120ffb702110000000fd81c26c0000000000000000000

1 output(s) for total of 440.185107881000 dcy

stealth address amount amount idx
00: 9a2cf7dbae184045ccda6889d0fb1ec365670a57f937642d30b3fe3a0e85e885 440.185107881000 78981 of 0

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": 43580, "vin": [ { "gen": { "height": 43570 } } ], "vout": [ { "amount": 440185107881, "target": { "key": "9a2cf7dbae184045ccda6889d0fb1ec365670a57f937642d30b3fe3a0e85e885" } } ], "extra": [ 1, 107, 199, 158, 182, 80, 172, 170, 230, 119, 89, 8, 181, 147, 23, 229, 156, 212, 103, 181, 211, 7, 34, 248, 54, 102, 67, 231, 228, 209, 32, 255, 183, 2, 17, 0, 0, 0, 15, 216, 28, 38, 192, 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