Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d991dfb6ec603404b20524e89c029c488333fbc0d81dddccc77a12448e82fe

Tx prefix hash: ee6db31ff6ecdac0ff994e9ed32eb129a8ce532d67664ac270aae9cd8e22dd5b
Tx public key: 2925d44aa08592af015c551cb66f71f619ab34a521f95844b2e417576fcee4c1
Timestamp: 1708627713 Timestamp [UCT]: 2024-02-22 18:48:33 Age [y:d:h:m:s]: 01:047:01:44:52
Block: 963273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294661 RingCT/type: yes/0
Extra: 012925d44aa08592af015c551cb66f71f619ab34a521f95844b2e417576fcee4c102110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 587c1504b82e00d872806b1be5a455c4c605046ddec95751d5e2af29c535bd4f 0.600000000000 1422974 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": 963283, "vin": [ { "gen": { "height": 963273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "587c1504b82e00d872806b1be5a455c4c605046ddec95751d5e2af29c535bd4f" } } ], "extra": [ 1, 41, 37, 212, 74, 160, 133, 146, 175, 1, 92, 85, 28, 182, 111, 113, 246, 25, 171, 52, 165, 33, 249, 88, 68, 178, 228, 23, 87, 111, 206, 228, 193, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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