Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f97952cd73e98a5be31ed1f669b7120e201492d1e0cb51e3b1c5c73d44e71b3

Tx prefix hash: 71825ab887638370434ec3c6c409531fbd7114669be18ba3cb8d846e1e255e52
Tx public key: baa1a8a246e9fdf57aedc39fda60d5d06cfd9da2404c164ad09fd7600ad80e45
Timestamp: 1716527675 Timestamp [UCT]: 2024-05-24 05:14:35 Age [y:d:h:m:s]: 00:313:17:42:44
Block: 1028779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224216 RingCT/type: yes/0
Extra: 01baa1a8a246e9fdf57aedc39fda60d5d06cfd9da2404c164ad09fd7600ad80e450211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c139f02a6576b613df238dc160306bf2ceff3a14564d14eed1f40b3de2863f07 0.600000000000 1496776 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": 1028789, "vin": [ { "gen": { "height": 1028779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c139f02a6576b613df238dc160306bf2ceff3a14564d14eed1f40b3de2863f07" } } ], "extra": [ 1, 186, 161, 168, 162, 70, 233, 253, 245, 122, 237, 195, 159, 218, 96, 213, 208, 108, 253, 157, 162, 64, 76, 22, 74, 208, 159, 215, 96, 10, 216, 14, 69, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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