Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83d78a6bfb51b962680ed9de9c794761ce939e4c7b1870e539a8c6dfd1b161a9

Tx prefix hash: ec1f5be811d82d0939c436859795f4520be9e2af612cf070165ff9abcda36071
Tx public key: 70c0c5e63b1973aafdca250b0e3dbda8d1428bb83137d5d388712e6108f1a18e
Timestamp: 1708104718 Timestamp [UCT]: 2024-02-16 17:31:58 Age [y:d:h:m:s]: 00:331:08:41:34
Block: 958934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237218 RingCT/type: yes/0
Extra: 0170c0c5e63b1973aafdca250b0e3dbda8d1428bb83137d5d388712e6108f1a18e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a236f52605c6455f6b19be08841ebf479d718b790a4583cea37dcacef22f7eec 0.600000000000 1418405 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": 958944, "vin": [ { "gen": { "height": 958934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a236f52605c6455f6b19be08841ebf479d718b790a4583cea37dcacef22f7eec" } } ], "extra": [ 1, 112, 192, 197, 230, 59, 25, 115, 170, 253, 202, 37, 11, 14, 61, 189, 168, 209, 66, 139, 184, 49, 55, 213, 211, 136, 113, 46, 97, 8, 241, 161, 142, 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