Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4f46eb356f76d57f4866f3b698c956db5318c3c709a08c905171f927c11928

Tx prefix hash: 9273169e9230d5ea552ef2e6facd6bbd16c6815e319a4e1d04c797a6a060ac55
Tx public key: 7681aa884741da168111b250e5bff44fa5f99d81720aa77986505e9c2684e25c
Timestamp: 1578652863 Timestamp [UCT]: 2020-01-10 10:41:03 Age [y:d:h:m:s]: 05:028:09:26:49
Block: 42517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170341 RingCT/type: yes/0
Extra: 017681aa884741da168111b250e5bff44fa5f99d81720aa77986505e9c2684e25c02110000000b4ac5aa02000000000000000000

1 output(s) for total of 443.735702814000 dcy

stealth address amount amount idx
00: e48bbd92f1dc8ea125c862f136fffc87e4a6680e6bfcf6e9460311ac62904d9f 443.735702814000 76646 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": 42527, "vin": [ { "gen": { "height": 42517 } } ], "vout": [ { "amount": 443735702814, "target": { "key": "e48bbd92f1dc8ea125c862f136fffc87e4a6680e6bfcf6e9460311ac62904d9f" } } ], "extra": [ 1, 118, 129, 170, 136, 71, 65, 218, 22, 129, 17, 178, 80, 229, 191, 244, 79, 165, 249, 157, 129, 114, 10, 167, 121, 134, 80, 94, 156, 38, 132, 226, 92, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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