Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ba5b3b46eb5bdd4593f81e6e70b6f00a17c62bfa1c2802faef5720a633360f5

Tx prefix hash: 40b3bc2792c097d1fb13eedce555f3211af951a7a3818321687decd7d106bcdf
Tx public key: abad3c09d5ceed9290edcead2b091c195cab73a6a7d31a9f69e5d88218b176a7
Timestamp: 1702827171 Timestamp [UCT]: 2023-12-17 15:32:51 Age [y:d:h:m:s]: 01:033:19:51:20
Block: 915182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285497 RingCT/type: yes/0
Extra: 01abad3c09d5ceed9290edcead2b091c195cab73a6a7d31a9f69e5d88218b176a702110000000833af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3985c380a8f60c969a1d91c7637278e9dbcaad48c17e1bcb14caf201cc653d5c 0.600000000000 1372568 of 15

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": 915192, "vin": [ { "gen": { "height": 915182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3985c380a8f60c969a1d91c7637278e9dbcaad48c17e1bcb14caf201cc653d5c" } } ], "extra": [ 1, 171, 173, 60, 9, 213, 206, 237, 146, 144, 237, 206, 173, 43, 9, 28, 25, 92, 171, 115, 166, 167, 211, 26, 159, 105, 229, 216, 130, 24, 177, 118, 167, 2, 17, 0, 0, 0, 8, 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