Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fa6c50d76fa430a9cb5c8ce80240b3a434e4f1b6381331f76d60836e80fe493

Tx prefix hash: b58c7fc805f543a0a0a67be4e420a4b6e56f0fcd5ba50f66562c367030b6f279
Tx public key: 579fe5226b75140ab11a9ba4c78c057f24e1f4dff488c527986181b18a09b0f1
Timestamp: 1755909035 Timestamp [UCT]: 2025-08-23 00:30:35 Age [y:d:h:m:s]: 00:095:14:02:07
Block: 1352337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68257 RingCT/type: yes/0
Extra: 01579fe5226b75140ab11a9ba4c78c057f24e1f4dff488c527986181b18a09b0f10211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 248f57cb5f44ca25ea9d13226a2a5a134415c611878f74221fde55a6c974876c 0.600000000000 1840300 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": 1352347, "vin": [ { "gen": { "height": 1352337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248f57cb5f44ca25ea9d13226a2a5a134415c611878f74221fde55a6c974876c" } } ], "extra": [ 1, 87, 159, 229, 34, 107, 117, 20, 10, 177, 26, 155, 164, 199, 140, 5, 127, 36, 225, 244, 223, 244, 136, 197, 39, 152, 97, 129, 177, 138, 9, 176, 241, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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