Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa06a1852bbd4d50b8a1a22943db214edd0a90fcbd8fe629a41c9c9fc25e6ab

Tx prefix hash: 9483ad47fd1ec763016324a99ba9e37efbfa0c474f286d52340227defc9b0de9
Tx public key: ccd8db042fa11746a4c74f328ee304b8c2b0b5aa42772421e8d29a719993f2b2
Timestamp: 1761834858 Timestamp [UCT]: 2025-10-30 14:34:18 Age [y:d:h:m:s]: 00:011:03:20:12
Block: 1401271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7967 RingCT/type: yes/0
Extra: 01ccd8db042fa11746a4c74f328ee304b8c2b0b5aa42772421e8d29a719993f2b2021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b9564063b283fd626955538cae6b7c1856f57715d7364c6e7eb076dea730376 0.600000000000 1889590 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": 1401281, "vin": [ { "gen": { "height": 1401271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b9564063b283fd626955538cae6b7c1856f57715d7364c6e7eb076dea730376" } } ], "extra": [ 1, 204, 216, 219, 4, 47, 161, 23, 70, 164, 199, 79, 50, 142, 227, 4, 184, 194, 176, 181, 170, 66, 119, 36, 33, 232, 210, 154, 113, 153, 147, 242, 178, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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