Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c6771e21abb21d5fa903a362e6fa8b9a3afa1c409b8d59862ee7c4ef7559f24

Tx prefix hash: 0823b41fd64bb7f9c9374d7c2b7aa62a9eab691bfdee2e9ab65738f3b808d883
Tx public key: 71de71ec69b54c8046fa171a15023f4767a573a724baffecb3f5345ff535ef7e
Timestamp: 1709023806 Timestamp [UCT]: 2024-02-27 08:50:06 Age [y:d:h:m:s]: 01:111:05:37:06
Block: 966563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340445 RingCT/type: yes/0
Extra: 0171de71ec69b54c8046fa171a15023f4767a573a724baffecb3f5345ff535ef7e0211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca8233df999523145692531e9ae55ea350518e2585fb5a557b3da5acb31317e2 0.600000000000 1426326 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": 966573, "vin": [ { "gen": { "height": 966563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca8233df999523145692531e9ae55ea350518e2585fb5a557b3da5acb31317e2" } } ], "extra": [ 1, 113, 222, 113, 236, 105, 181, 76, 128, 70, 250, 23, 26, 21, 2, 63, 71, 103, 165, 115, 167, 36, 186, 255, 236, 179, 245, 52, 95, 245, 53, 239, 126, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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