Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5535c8644548786e260fb07797b1403a11cf4b6b04fef613450afd193ff0d67

Tx prefix hash: f449dcbb05ee8a3f605acf6bbd48d4d8aa44c664682f3e51cc6c76e682e38a9d
Tx public key: c91a67e8b71bcf59c029016471e3516623483017805d3df350a73baa4f967769
Timestamp: 1734246870 Timestamp [UCT]: 2024-12-15 07:14:30 Age [y:d:h:m:s]: 01:001:12:58:22
Block: 1175572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259505 RingCT/type: yes/0
Extra: 01c91a67e8b71bcf59c029016471e3516623483017805d3df350a73baa4f967769021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 031fd0b5dae7c5ba66f6b9889beb6f55a8f99b97e77ea5aa315554d36dbb9fdd 0.600000000000 1661871 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": 1175582, "vin": [ { "gen": { "height": 1175572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "031fd0b5dae7c5ba66f6b9889beb6f55a8f99b97e77ea5aa315554d36dbb9fdd" } } ], "extra": [ 1, 201, 26, 103, 232, 183, 27, 207, 89, 192, 41, 1, 100, 113, 227, 81, 102, 35, 72, 48, 23, 128, 93, 61, 243, 80, 167, 59, 170, 79, 150, 119, 105, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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