Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d651c896741fc74a08300dfb208d9ca49bd970ceba9255f33d612ff3ff262a70

Tx prefix hash: 10f85ca34a03871e761366a7be8b70bde66e172bcdb8403ef9ad3419cf5ac425
Tx public key: 009c4e457b2f6dff602ee5ce17ce7c68dffd437542164894a6e5a6bd36c6232a
Timestamp: 1577160223 Timestamp [UCT]: 2019-12-24 04:03:43 Age [y:d:h:m:s]: 05:071:15:24:26
Block: 30332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201113 RingCT/type: yes/0
Extra: 01009c4e457b2f6dff602ee5ce17ce7c68dffd437542164894a6e5a6bd36c6232a02110000001a398c17aa000000000000000000

1 output(s) for total of 486.965679969000 dcy

stealth address amount amount idx
00: ffa070a045178bd4a9ba469fba4abe3fd350d8625cfd85f5b662f106206743ca 486.965679969000 50084 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": 30342, "vin": [ { "gen": { "height": 30332 } } ], "vout": [ { "amount": 486965679969, "target": { "key": "ffa070a045178bd4a9ba469fba4abe3fd350d8625cfd85f5b662f106206743ca" } } ], "extra": [ 1, 0, 156, 78, 69, 123, 47, 109, 255, 96, 46, 229, 206, 23, 206, 124, 104, 223, 253, 67, 117, 66, 22, 72, 148, 166, 229, 166, 189, 54, 198, 35, 42, 2, 17, 0, 0, 0, 26, 57, 140, 23, 170, 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