Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f7501746381dd8875cd80c216b67621291fcfa0c13543c7cb57733ac1f4a4e1

Tx prefix hash: 2f9e8caa466caf32445520328194bdabf02e1aa49dbf2d455bcdfa5a672c091b
Tx public key: 0164d825696ac5c8d9e981524b0ac725de3559c36f522fae4c25bb9565223926
Timestamp: 1684927364 Timestamp [UCT]: 2023-05-24 11:22:44 Age [y:d:h:m:s]: 01:320:08:46:16
Block: 767038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490168 RingCT/type: yes/0
Extra: 010164d825696ac5c8d9e981524b0ac725de3559c36f522fae4c25bb956522392602110000000533af99f4000000000000000000

1 output(s) for total of 1.763944317000 dcy

stealth address amount amount idx
00: d6ceaa4acd8d0cee10ca111c529fa8d15e2d78ca163457ff52fd2967c523d9a2 1.763944317000 1216135 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": 767048, "vin": [ { "gen": { "height": 767038 } } ], "vout": [ { "amount": 1763944317, "target": { "key": "d6ceaa4acd8d0cee10ca111c529fa8d15e2d78ca163457ff52fd2967c523d9a2" } } ], "extra": [ 1, 1, 100, 216, 37, 105, 106, 197, 200, 217, 233, 129, 82, 75, 10, 199, 37, 222, 53, 89, 195, 111, 82, 47, 174, 76, 37, 187, 149, 101, 34, 57, 38, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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