Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479c95afa77ee033ab40c40fa348ca0d872c7b2d2a267affcfc0fd092abcbff3

Tx prefix hash: 8af0b0ffd714a677f24cb851052436af2817560aa9d9d546ec948db67f216874
Tx public key: b941a7d68080a6f45a69109394675612d306cf8cd6610f88b8ed7c835deeb6b8
Timestamp: 1719886447 Timestamp [UCT]: 2024-07-02 02:14:07 Age [y:d:h:m:s]: 01:157:10:48:56
Block: 1056611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371097 RingCT/type: yes/0
Extra: 01b941a7d68080a6f45a69109394675612d306cf8cd6610f88b8ed7c835deeb6b80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fea6cf5841b9a1240e1635b58fc6ee5d4ec5d977076a4ed9658df22f744dc5a4 0.600000000000 1527026 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": 1056621, "vin": [ { "gen": { "height": 1056611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fea6cf5841b9a1240e1635b58fc6ee5d4ec5d977076a4ed9658df22f744dc5a4" } } ], "extra": [ 1, 185, 65, 167, 214, 128, 128, 166, 244, 90, 105, 16, 147, 148, 103, 86, 18, 211, 6, 207, 140, 214, 97, 15, 136, 184, 237, 124, 131, 93, 238, 182, 184, 2, 17, 0, 0, 0, 1, 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