Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5daafffaaf95deddec3cd0cd4b73bfd050c3eccd64e742a6023dde047c21b85f

Tx prefix hash: dad4060b094e473580bb0b8271c96ec6d4b2a92b9697c804c2719ccebb0b9f21
Tx public key: dc44c6aa66f247043de723b397b9e647414f34746d98f2ee163d7ca99d07eba9
Timestamp: 1735692921 Timestamp [UCT]: 2025-01-01 00:55:21 Age [y:d:h:m:s]: 00:324:03:09:41
Block: 1187523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229169 RingCT/type: yes/0
Extra: 01dc44c6aa66f247043de723b397b9e647414f34746d98f2ee163d7ca99d07eba90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96501a9c54d5ae49385aa3642b8b4d32255fa9fc9b0b10fb594558a86c7a1f2e 0.600000000000 1674014 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": 1187533, "vin": [ { "gen": { "height": 1187523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96501a9c54d5ae49385aa3642b8b4d32255fa9fc9b0b10fb594558a86c7a1f2e" } } ], "extra": [ 1, 220, 68, 198, 170, 102, 242, 71, 4, 61, 231, 35, 179, 151, 185, 230, 71, 65, 79, 52, 116, 109, 152, 242, 238, 22, 61, 124, 169, 157, 7, 235, 169, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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