Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 535cb2932a9e74c50f4c0bf8fdc6222bda0fb2ee652184209eac19bdde417c37

Tx prefix hash: 5520b950267835bee333b0ba3b5c9d67c3e9fba21220daa6e0adb151c7f2334e
Tx public key: 79eac6ddc28e36e903e1b1b13b8c8ed010566ceebd4d9efbff19937fab17400e
Timestamp: 1649622404 Timestamp [UCT]: 2022-04-10 20:26:44 Age [y:d:h:m:s]: 02:259:05:02:55
Block: 477496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705056 RingCT/type: yes/0
Extra: 0179eac6ddc28e36e903e1b1b13b8c8ed010566ceebd4d9efbff19937fab17400e021100000007a8c141c5000000000000000000

1 output(s) for total of 16.066200804000 dcy

stealth address amount amount idx
00: b310408d12c65af475c7dc96e2a50f6d036a56baafa9f6c66bb6aa9abbcd1cf3 16.066200804000 898163 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": 477506, "vin": [ { "gen": { "height": 477496 } } ], "vout": [ { "amount": 16066200804, "target": { "key": "b310408d12c65af475c7dc96e2a50f6d036a56baafa9f6c66bb6aa9abbcd1cf3" } } ], "extra": [ 1, 121, 234, 198, 221, 194, 142, 54, 233, 3, 225, 177, 177, 59, 140, 142, 208, 16, 86, 108, 238, 189, 77, 158, 251, 255, 25, 147, 127, 171, 23, 64, 14, 2, 17, 0, 0, 0, 7, 168, 193, 65, 197, 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