Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ade1c56cf5d04d75613415c053f482c3b302ae07664e2b1c3dd5f38a245d04c9

Tx prefix hash: 497d73cca45f568ce7e3edf673a2fa467d35a15ffe0193fb41b602e2e62e3fd1
Tx public key: 3c478a62ee4a2a678c9d9d651a4b0d09fbf29d94b5f570c59227e270c8ac8c01
Timestamp: 1577562440 Timestamp [UCT]: 2019-12-28 19:47:20 Age [y:d:h:m:s]: 05:002:17:32:01
Block: 33774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151966 RingCT/type: yes/0
Extra: 013c478a62ee4a2a678c9d9d651a4b0d09fbf29d94b5f570c59227e270c8ac8c01021100000005d81c26c0000000000000000000

1 output(s) for total of 474.344177989000 dcy

stealth address amount amount idx
00: 6513a5bf6201359f671e4c117f20a8854b0c513dde0cf3ab8ff4261350797f21 474.344177989000 56663 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": 33784, "vin": [ { "gen": { "height": 33774 } } ], "vout": [ { "amount": 474344177989, "target": { "key": "6513a5bf6201359f671e4c117f20a8854b0c513dde0cf3ab8ff4261350797f21" } } ], "extra": [ 1, 60, 71, 138, 98, 238, 74, 42, 103, 140, 157, 157, 101, 26, 75, 13, 9, 251, 242, 157, 148, 181, 245, 112, 197, 146, 39, 226, 112, 200, 172, 140, 1, 2, 17, 0, 0, 0, 5, 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