Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689c968447d1563546504f7535ad22f941b4a30d7df16c3ff680eef8d72638e0

Tx prefix hash: 6916bd67731316cdff8af45b915664bc06f7d4557cde096e78e8e1a7b086c72b
Tx public key: 79eda30b83907e0113af07a66e14e33d3b1577f445a2dfaa59a92caf40258e33
Timestamp: 1724634320 Timestamp [UCT]: 2024-08-26 01:05:20 Age [y:d:h:m:s]: 00:233:10:41:28
Block: 1095965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166722 RingCT/type: yes/0
Extra: 0179eda30b83907e0113af07a66e14e33d3b1577f445a2dfaa59a92caf40258e3302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 762f3b2b9fb8ab81ba4730f7aa5232e748453322bad012ea8392e5c22c94cc9e 0.600000000000 1571150 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": 1095975, "vin": [ { "gen": { "height": 1095965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "762f3b2b9fb8ab81ba4730f7aa5232e748453322bad012ea8392e5c22c94cc9e" } } ], "extra": [ 1, 121, 237, 163, 11, 131, 144, 126, 1, 19, 175, 7, 166, 110, 20, 227, 61, 59, 21, 119, 244, 69, 162, 223, 170, 89, 169, 44, 175, 64, 37, 142, 51, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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