Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ba0744de4e9e381b8dcbce568d05e2e2436c6b8caa686b6465a3528c1f1e19

Tx prefix hash: d435703d0f430650bd3127fd34d06cb28165163e5af041f1b65d77da9720eddd
Tx public key: 35b145e828e7d1465ed199e58cadf80bf2c326ab519f94a0106fd212fa14c7f2
Timestamp: 1702709336 Timestamp [UCT]: 2023-12-16 06:48:56 Age [y:d:h:m:s]: 01:111:14:05:51
Block: 914206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340883 RingCT/type: yes/0
Extra: 0135b145e828e7d1465ed199e58cadf80bf2c326ab519f94a0106fd212fa14c7f202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73d3baee80a2b2b45f0f1a0f73393dff35d5edbc91e562f8bd968e922733261e 0.600000000000 1371492 of 15

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": 914216, "vin": [ { "gen": { "height": 914206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73d3baee80a2b2b45f0f1a0f73393dff35d5edbc91e562f8bd968e922733261e" } } ], "extra": [ 1, 53, 177, 69, 232, 40, 231, 209, 70, 94, 209, 153, 229, 140, 173, 248, 11, 242, 195, 38, 171, 81, 159, 148, 160, 16, 111, 210, 18, 250, 20, 199, 242, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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