Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16b6fe891c3e6bbe95b6cb84b1842769156bb0cbb30b3ef72f8b724065dd3746

Tx prefix hash: 43e9492f49cb683456d47661d6b65a2fa825c7c14236296398a70fa155471ad2
Tx public key: ccdf77e2975e15600914fb0a13d595d9ec9005e9f1ac72b03fd89a290a6276b2
Timestamp: 1577673302 Timestamp [UCT]: 2019-12-30 02:35:02 Age [y:d:h:m:s]: 05:066:03:07:05
Block: 34719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197025 RingCT/type: yes/0
Extra: 01ccdf77e2975e15600914fb0a13d595d9ec9005e9f1ac72b03fd89a290a6276b20211000000028a2ee0d9000000000000000000

1 output(s) for total of 470.936547741000 dcy

stealth address amount amount idx
00: 0ca4ed021811848c6a3ba27a34f3084e560d492440f6b0d13b844091b0d862b4 470.936547741000 58465 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": 34729, "vin": [ { "gen": { "height": 34719 } } ], "vout": [ { "amount": 470936547741, "target": { "key": "0ca4ed021811848c6a3ba27a34f3084e560d492440f6b0d13b844091b0d862b4" } } ], "extra": [ 1, 204, 223, 119, 226, 151, 94, 21, 96, 9, 20, 251, 10, 19, 213, 149, 217, 236, 144, 5, 233, 241, 172, 114, 176, 63, 216, 154, 41, 10, 98, 118, 178, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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