Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0d301e655c9dc8c072102b32a713d566ad88175e30f4dfe083bf8cf32e5eafb

Tx prefix hash: ee3ee68238be43a8f955c8680a9afd30078f22f13f3c1a60902fe837fbb31f90
Tx public key: fc2b4753d34d75daf481b8c2a4bca80a2da1aea98d013d5a2d7e2cab6f4f1def
Timestamp: 1761321011 Timestamp [UCT]: 2025-10-24 15:50:11 Age [y:d:h:m:s]: 00:017:07:32:27
Block: 1397025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12378 RingCT/type: yes/0
Extra: 01fc2b4753d34d75daf481b8c2a4bca80a2da1aea98d013d5a2d7e2cab6f4f1def021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 927cf543bcc5d58a98ae28abd7d2700f38315bb60e6e90503999b4c3ec5de916 0.600000000000 1885316 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": 1397035, "vin": [ { "gen": { "height": 1397025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "927cf543bcc5d58a98ae28abd7d2700f38315bb60e6e90503999b4c3ec5de916" } } ], "extra": [ 1, 252, 43, 71, 83, 211, 77, 117, 218, 244, 129, 184, 194, 164, 188, 168, 10, 45, 161, 174, 169, 141, 1, 61, 90, 45, 126, 44, 171, 111, 79, 29, 239, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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