Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 762ad4a14a61f96235f76a1e2f329ac4f72620f06dcd4742182cdbb69ba5fc77

Tx prefix hash: 53b59d9cafbcf1085afa7cbb875eac5e27dc602b2cb5e40e23108c9f2a49b51e
Tx public key: fd17f4f0544e5852564586a13f5437f3c7307743d22c2fe390797e74f7669bae
Timestamp: 1737341033 Timestamp [UCT]: 2025-01-20 02:43:53 Age [y:d:h:m:s]: 00:303:23:31:31
Block: 1201126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214811 RingCT/type: yes/0
Extra: 01fd17f4f0544e5852564586a13f5437f3c7307743d22c2fe390797e74f7669bae0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db76e6697c69b11191f8e3dc9817b4346ddb6266d5b738e8a342601ba068c66 0.600000000000 1687775 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": 1201136, "vin": [ { "gen": { "height": 1201126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db76e6697c69b11191f8e3dc9817b4346ddb6266d5b738e8a342601ba068c66" } } ], "extra": [ 1, 253, 23, 244, 240, 84, 78, 88, 82, 86, 69, 134, 161, 63, 84, 55, 243, 199, 48, 119, 67, 210, 44, 47, 227, 144, 121, 126, 116, 247, 102, 155, 174, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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