Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc566e9f8a0d29b4ecea412de02eae5fb13c4042d8c37e60dc7702110177010

Tx prefix hash: 3ef3cb85d13dd0b64a5a152a07e7b5809a5be9f31560e1ffe67ac8f1d07d3025
Tx public key: be1b9b959727ce58cf8d35e512050f87167c7643e77cefec455a3c5ddfa6207a
Timestamp: 1721270400 Timestamp [UCT]: 2024-07-18 02:40:00 Age [y:d:h:m:s]: 00:262:15:46:19
Block: 1068104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187616 RingCT/type: yes/0
Extra: 01be1b9b959727ce58cf8d35e512050f87167c7643e77cefec455a3c5ddfa6207a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05e03b4d100a71e11bd5085af6b6a48009b6943f6b181a4032158562bf8d0d6e 0.600000000000 1539119 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": 1068114, "vin": [ { "gen": { "height": 1068104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05e03b4d100a71e11bd5085af6b6a48009b6943f6b181a4032158562bf8d0d6e" } } ], "extra": [ 1, 190, 27, 155, 149, 151, 39, 206, 88, 207, 141, 53, 229, 18, 5, 15, 135, 22, 124, 118, 67, 231, 124, 239, 236, 69, 90, 60, 93, 223, 166, 32, 122, 2, 17, 0, 0, 0, 2, 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