Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 168e06910fc0585ec48dc24d38e01ce9a28e5c4d1107ccb0df3c7083d5115585

Tx prefix hash: 187cfaa239e5195dd1c3d95a1320c2a7e9fec8e1eb8d855d0b00ae695d508e6e
Tx public key: 165dd2413fcd0de49383cafdde04f6efb5fa0c31be6879f3cf8dd4c293635d11
Timestamp: 1579272060 Timestamp [UCT]: 2020-01-17 14:41:00 Age [y:d:h:m:s]: 05:157:03:16:45
Block: 47626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1262296 RingCT/type: yes/0
Extra: 01165dd2413fcd0de49383cafdde04f6efb5fa0c31be6879f3cf8dd4c293635d11021100000005b221b3d1000000000000000000

1 output(s) for total of 426.772206187000 dcy

stealth address amount amount idx
00: f934e1c2568282fa55405bf5a1a47543985d9b59673d5278030e5422c4be9364 426.772206187000 88008 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": 47636, "vin": [ { "gen": { "height": 47626 } } ], "vout": [ { "amount": 426772206187, "target": { "key": "f934e1c2568282fa55405bf5a1a47543985d9b59673d5278030e5422c4be9364" } } ], "extra": [ 1, 22, 93, 210, 65, 63, 205, 13, 228, 147, 131, 202, 253, 222, 4, 246, 239, 181, 250, 12, 49, 190, 104, 121, 243, 207, 141, 212, 194, 147, 99, 93, 17, 2, 17, 0, 0, 0, 5, 178, 33, 179, 209, 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