Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 431f797345cd54faa36fd83cbef2dd6cf696c9bd32014cd9b4f5828cf8a8c426

Tx prefix hash: ea72f9fdc44737cb7d08e5b9f6764d94f8d03bca932ff1497f95782e7b39e247
Tx public key: d2ae8be58365a10b15b0529318bd98d3bfc76c462bee62be97f5ca8c3d949bce
Timestamp: 1676226894 Timestamp [UCT]: 2023-02-12 18:34:54 Age [y:d:h:m:s]: 02:065:12:43:21
Block: 695544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 568443 RingCT/type: yes/0
Extra: 01d2ae8be58365a10b15b0529318bd98d3bfc76c462bee62be97f5ca8c3d949bce0211000000015029cbac000000000000000000

1 output(s) for total of 3.043504259000 dcy

stealth address amount amount idx
00: 260b386078f0b35ef15f5a5bd5ec222f96c1b425ada870b0ebfa28c6435aee9e 3.043504259000 1138501 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": 695554, "vin": [ { "gen": { "height": 695544 } } ], "vout": [ { "amount": 3043504259, "target": { "key": "260b386078f0b35ef15f5a5bd5ec222f96c1b425ada870b0ebfa28c6435aee9e" } } ], "extra": [ 1, 210, 174, 139, 229, 131, 101, 161, 11, 21, 176, 82, 147, 24, 189, 152, 211, 191, 199, 108, 70, 43, 238, 98, 190, 151, 245, 202, 140, 61, 148, 155, 206, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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