Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a6d526ced2459bfc1fad60c9b4e81046853d10319f8617e3ae9a6c0dc89f61

Tx prefix hash: 7e530bd3ccd67d1e3b24985ffcb61a415b2e4163c147db4916af1322a8183013
Tx public key: 631b75ca4349aff0cb85a6f13a77147e7525a9e435e21fa9e710a8d1b3adc987
Timestamp: 1697299564 Timestamp [UCT]: 2023-10-14 16:06:04 Age [y:d:h:m:s]: 01:248:10:18:14
Block: 869559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438492 RingCT/type: yes/0
Extra: 01631b75ca4349aff0cb85a6f13a77147e7525a9e435e21fa9e710a8d1b3adc98702110000000675e3f0e9000000000000000000

1 output(s) for total of 0.806844959000 dcy

stealth address amount amount idx
00: d0c9685ac8bb576de97fc06ef0a7fc2287bf11c939dfb830dd5e5ac803acd682 0.806844959000 1324408 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": 869569, "vin": [ { "gen": { "height": 869559 } } ], "vout": [ { "amount": 806844959, "target": { "key": "d0c9685ac8bb576de97fc06ef0a7fc2287bf11c939dfb830dd5e5ac803acd682" } } ], "extra": [ 1, 99, 27, 117, 202, 67, 73, 175, 240, 203, 133, 166, 241, 58, 119, 20, 126, 117, 37, 169, 228, 53, 226, 31, 169, 231, 16, 168, 209, 179, 173, 201, 135, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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