Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c279a5d56512e7f473ad78a96eac76a0fd8d49e3d533653174e9638bdc931e

Tx prefix hash: d409804175c976313f7f15e88ad29b7c54e3237be56320741792f82325313a0e
Tx public key: ac8be8e6c4a5ae22d91d75307bea045664406425e226bac80fe78a14e79fe851
Timestamp: 1760408546 Timestamp [UCT]: 2025-10-14 02:22:26 Age [y:d:h:m:s]: 00:070:17:52:50
Block: 1389456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50640 RingCT/type: yes/0
Extra: 01ac8be8e6c4a5ae22d91d75307bea045664406425e226bac80fe78a14e79fe851021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2b6f1c720ba7fbdf5ee542522e608c5f15f7554109b4b9f8598c6b556091f79 0.600000000000 1877685 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": 1389466, "vin": [ { "gen": { "height": 1389456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2b6f1c720ba7fbdf5ee542522e608c5f15f7554109b4b9f8598c6b556091f79" } } ], "extra": [ 1, 172, 139, 232, 230, 196, 165, 174, 34, 217, 29, 117, 48, 123, 234, 4, 86, 100, 64, 100, 37, 226, 38, 186, 200, 15, 231, 138, 20, 231, 159, 232, 81, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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