Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52be6e1fc65e5c2a04a3357b87fe41512d4dd9db39ba8bdb33c72d1bc018bbd0

Tx prefix hash: 6d9411d73dbfbf1cc4c3b631de76b7d368b6697a8b272762400ac2986446afd4
Tx public key: aee9233c2fd39803d6eb08e2ff9e47229e254f9ae6f870474837f70aa7c37b10
Timestamp: 1763274337 Timestamp [UCT]: 2025-11-16 06:25:37 Age [y:d:h:m:s]: 00:012:03:32:17
Block: 1413189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8704 RingCT/type: yes/0
Extra: 01aee9233c2fd39803d6eb08e2ff9e47229e254f9ae6f870474837f70aa7c37b1002110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7b9322eafd0aede4615e2fa337e7ae92eac875c7c01b9411e98010f19542ed3 0.600000000000 1901666 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": 1413199, "vin": [ { "gen": { "height": 1413189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7b9322eafd0aede4615e2fa337e7ae92eac875c7c01b9411e98010f19542ed3" } } ], "extra": [ 1, 174, 233, 35, 60, 47, 211, 152, 3, 214, 235, 8, 226, 255, 158, 71, 34, 158, 37, 79, 154, 230, 248, 112, 71, 72, 55, 247, 10, 167, 195, 123, 16, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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