Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 140096355ca06f7e55a71000f0227aa0501a196c0180f9979d717df629771eb8

Tx prefix hash: 0f5d2c5d75031733302d784f6051d6b7b15e0f23e170a1d2d9a629585b3e327f
Tx public key: 578baf9288af12fb0d77571a8d216a8b9a325e9fa54abff5ad0ce5075d1d37ee
Timestamp: 1660640938 Timestamp [UCT]: 2022-08-16 09:08:58 Age [y:d:h:m:s]: 02:182:06:40:16
Block: 567001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651465 RingCT/type: yes/0
Extra: 01578baf9288af12fb0d77571a8d216a8b9a325e9fa54abff5ad0ce5075d1d37ee021100000009ec6d1a1a000000000000000000

1 output(s) for total of 8.115035444000 dcy

stealth address amount amount idx
00: c2fc27b147b24f25e8f1fe5238e2ecf08ae255431e5a3e2e017587d94d8a5710 8.115035444000 1000048 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": 567011, "vin": [ { "gen": { "height": 567001 } } ], "vout": [ { "amount": 8115035444, "target": { "key": "c2fc27b147b24f25e8f1fe5238e2ecf08ae255431e5a3e2e017587d94d8a5710" } } ], "extra": [ 1, 87, 139, 175, 146, 136, 175, 18, 251, 13, 119, 87, 26, 141, 33, 106, 139, 154, 50, 94, 159, 165, 74, 191, 245, 173, 12, 229, 7, 93, 29, 55, 238, 2, 17, 0, 0, 0, 9, 236, 109, 26, 26, 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