Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4af0198c932996454a019c7216ed9ca717ef5f982f5bad58f23f224e13d91052

Tx prefix hash: e576952744f2d67cfbd0f95d5085055bf09581bae735472664870afc0cd8eebe
Tx public key: 76a1acd9e1edb39738ad17fd16d3cab68df212b00a68ae143407e4c71bf471d3
Timestamp: 1649639049 Timestamp [UCT]: 2022-04-11 01:04:09 Age [y:d:h:m:s]: 02:338:05:41:05
Block: 477633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761316 RingCT/type: yes/0
Extra: 0176a1acd9e1edb39738ad17fd16d3cab68df212b00a68ae143407e4c71bf471d30211000000014da16a3a000000000000000000

1 output(s) for total of 16.047368827000 dcy

stealth address amount amount idx
00: f42d49a2e0bbcd9e750e981e833ac5f4422037d80269fc0d4079784b466d9941 16.047368827000 898310 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": 477643, "vin": [ { "gen": { "height": 477633 } } ], "vout": [ { "amount": 16047368827, "target": { "key": "f42d49a2e0bbcd9e750e981e833ac5f4422037d80269fc0d4079784b466d9941" } } ], "extra": [ 1, 118, 161, 172, 217, 225, 237, 179, 151, 56, 173, 23, 253, 22, 211, 202, 182, 141, 242, 18, 176, 10, 104, 174, 20, 52, 7, 228, 199, 27, 244, 113, 211, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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