Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57d2d04c766bd945575c4a3a94d996355734e9f58d05be422bef0346bedad52c

Tx prefix hash: d66f74ab368f7763ed9737e79a6d9e9606831eb3e256b72dedd23fc3014ba198
Tx public key: fcacd9ca2cb848ff6414678c35ed20f0a804b19448013b26a3bb1f65ae045a9a
Timestamp: 1697651157 Timestamp [UCT]: 2023-10-18 17:45:57 Age [y:d:h:m:s]: 01:191:04:22:14
Block: 872475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397677 RingCT/type: yes/0
Extra: 01fcacd9ca2cb848ff6414678c35ed20f0a804b19448013b26a3bb1f65ae045a9a02110000000933af99f4000000000000000000

1 output(s) for total of 0.789092957000 dcy

stealth address amount amount idx
00: 7d64e9a6c8a67f5ff8e24b02f39da62571dfb2344f244606501c082784ef7e18 0.789092957000 1327563 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": 872485, "vin": [ { "gen": { "height": 872475 } } ], "vout": [ { "amount": 789092957, "target": { "key": "7d64e9a6c8a67f5ff8e24b02f39da62571dfb2344f244606501c082784ef7e18" } } ], "extra": [ 1, 252, 172, 217, 202, 44, 184, 72, 255, 100, 20, 103, 140, 53, 237, 32, 240, 168, 4, 177, 148, 72, 1, 59, 38, 163, 187, 31, 101, 174, 4, 90, 154, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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