Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5966bc12834f23e1bc2098d78b160829afc5624af114dc3b95b8d49aee68c1a

Tx prefix hash: fa590dcfa8e0fa07860aad041d39d130675326c20defe1545193411ae983ce12
Tx public key: aa2a9968aeadcb15d546a0260db60d8d32fd41215bfbee343219f3b296157cc5
Timestamp: 1578831163 Timestamp [UCT]: 2020-01-12 12:12:43 Age [y:d:h:m:s]: 05:294:02:31:08
Block: 43926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358068 RingCT/type: yes/0
Extra: 01aa2a9968aeadcb15d546a0260db60d8d32fd41215bfbee343219f3b296157cc50211000000134943cd9f000000000000000000

1 output(s) for total of 438.991154364000 dcy

stealth address amount amount idx
00: e4bfc150429c7e51e363291d400942b65dbdaf27a029076a226d68b8aac32099 438.991154364000 79736 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": 43936, "vin": [ { "gen": { "height": 43926 } } ], "vout": [ { "amount": 438991154364, "target": { "key": "e4bfc150429c7e51e363291d400942b65dbdaf27a029076a226d68b8aac32099" } } ], "extra": [ 1, 170, 42, 153, 104, 174, 173, 203, 21, 213, 70, 160, 38, 13, 182, 13, 141, 50, 253, 65, 33, 91, 251, 238, 52, 50, 25, 243, 178, 150, 21, 124, 197, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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