Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92aad394cd0a8f0bed4c09d78bc13b81b5c4896f085d0f71612976f1384eca5b

Tx prefix hash: f6d142491aff79ab15f7f7c5f513626bb572b18af942f46d2a1bd4e25aa63581
Tx public key: 8e46e8e3e29f0d73a9c90fc72715def570008a90e2adc97aa90078d19d40072a
Timestamp: 1676205513 Timestamp [UCT]: 2023-02-12 12:38:33 Age [y:d:h:m:s]: 02:053:12:48:41
Block: 695365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559854 RingCT/type: yes/0
Extra: 018e46e8e3e29f0d73a9c90fc72715def570008a90e2adc97aa90078d19d40072a0211000000015029cbac000000000000000000

1 output(s) for total of 3.047663511000 dcy

stealth address amount amount idx
00: ec80605202cf8354857eeacd10b2637fd7103e1c34f79cabc4db38a20ca904a8 3.047663511000 1138320 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": 695375, "vin": [ { "gen": { "height": 695365 } } ], "vout": [ { "amount": 3047663511, "target": { "key": "ec80605202cf8354857eeacd10b2637fd7103e1c34f79cabc4db38a20ca904a8" } } ], "extra": [ 1, 142, 70, 232, 227, 226, 159, 13, 115, 169, 201, 15, 199, 39, 21, 222, 245, 112, 0, 138, 144, 226, 173, 201, 122, 169, 0, 120, 209, 157, 64, 7, 42, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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