Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899537d2c53c0d308a4c6fa05825ee392b50ce1e15bf41fbf6829f3e9f9b08fb

Tx prefix hash: 7cf8e5d348a9112d13fc1d6ad859f3667689622268a515178c2cc87afcb6bd67
Tx public key: d4afb6366dc9533f2e3d38ef50b7c6ecdd910d0ac2ac1e918bed130f5d3844e5
Timestamp: 1581903808 Timestamp [UCT]: 2020-02-17 01:43:28 Age [y:d:h:m:s]: 04:275:22:14:51
Block: 66376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089649 RingCT/type: yes/0
Extra: 01d4afb6366dc9533f2e3d38ef50b7c6ecdd910d0ac2ac1e918bed130f5d3844e5021100000001c71d3ff9000000000000000000

1 output(s) for total of 369.887425060000 dcy

stealth address amount amount idx
00: bd4953d10d4356cf1a534c61326f830811115cd2c670c7b8644f5cae4a92e9ea 369.887425060000 122293 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": 66386, "vin": [ { "gen": { "height": 66376 } } ], "vout": [ { "amount": 369887425060, "target": { "key": "bd4953d10d4356cf1a534c61326f830811115cd2c670c7b8644f5cae4a92e9ea" } } ], "extra": [ 1, 212, 175, 182, 54, 109, 201, 83, 63, 46, 61, 56, 239, 80, 183, 198, 236, 221, 145, 13, 10, 194, 172, 30, 145, 139, 237, 19, 15, 93, 56, 68, 229, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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