Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f50654e30db39e9670b24b0ac2ed8d7231fef5da749fdb3e10f38c5d917b1a

Tx prefix hash: 006986ccfdae48cdc06afa7655cd8b3c3a6fb174643223ddeac814afc41242f7
Tx public key: a0c7374821a7f4267b7b7fea46c57b0e4ec150fb82793c063dd520a3e58cd9a0
Timestamp: 1577686473 Timestamp [UCT]: 2019-12-30 06:14:33 Age [y:d:h:m:s]: 04:336:00:20:08
Block: 34818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129272 RingCT/type: yes/0
Extra: 01a0c7374821a7f4267b7b7fea46c57b0e4ec150fb82793c063dd520a3e58cd9a00211000000028a2ee0d9000000000000000000

1 output(s) for total of 470.580977572000 dcy

stealth address amount amount idx
00: 267cd1c0d091d0b01b289fcf4daf09f6801b82e3e1ceb1f6cf8889ba18b374ec 470.580977572000 58657 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": 34828, "vin": [ { "gen": { "height": 34818 } } ], "vout": [ { "amount": 470580977572, "target": { "key": "267cd1c0d091d0b01b289fcf4daf09f6801b82e3e1ceb1f6cf8889ba18b374ec" } } ], "extra": [ 1, 160, 199, 55, 72, 33, 167, 244, 38, 123, 123, 127, 234, 70, 197, 123, 14, 78, 193, 80, 251, 130, 121, 60, 6, 61, 213, 32, 163, 229, 140, 217, 160, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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