Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 011d330db8d687bab591062b59902523abf81570746a467a087e40eeeee3180d

Tx prefix hash: 0dacbce522ff6e4a6af47db24f4605ff957ef0a24b2a0e4149ff5c24e99d25a1
Tx public key: 91051e75346a0347181027d0f3a40f78d551e5c7d309373ef27a14053482b9e9
Timestamp: 1697813391 Timestamp [UCT]: 2023-10-20 14:49:51 Age [y:d:h:m:s]: 01:215:09:54:52
Block: 873824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415017 RingCT/type: yes/0
Extra: 0191051e75346a0347181027d0f3a40f78d551e5c7d309373ef27a14053482b9e902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.781013189000 dcy

stealth address amount amount idx
00: aa63aca16c43efa78598d077165b70211a607815be9ecbb15400b58dbc01db66 0.781013189000 1328998 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": 873834, "vin": [ { "gen": { "height": 873824 } } ], "vout": [ { "amount": 781013189, "target": { "key": "aa63aca16c43efa78598d077165b70211a607815be9ecbb15400b58dbc01db66" } } ], "extra": [ 1, 145, 5, 30, 117, 52, 106, 3, 71, 24, 16, 39, 208, 243, 164, 15, 120, 213, 81, 229, 199, 211, 9, 55, 62, 242, 122, 20, 5, 52, 130, 185, 233, 2, 17, 0, 0, 0, 2, 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