Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd103e1a975ca772f16b3eb3481f9d1fe5ab65aaf13c67df50f0bb8a73b1b8b5

Tx prefix hash: 70e40691b2b61f9db772589cb4c52aa9628a90b61e5733a6ec8a443c9270592b
Tx public key: 378511fab4fa29a3e53bc94e9875971bc893b42e850725f26019aed822d383cb
Timestamp: 1725675188 Timestamp [UCT]: 2024-09-07 02:13:08 Age [y:d:h:m:s]: 00:193:08:15:20
Block: 1104609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138032 RingCT/type: yes/0
Extra: 01378511fab4fa29a3e53bc94e9875971bc893b42e850725f26019aed822d383cb021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8b6b9d494d1980fb73b6384914fbb6356e978a9e6195a8c9556df9a1ed1713d 0.600000000000 1581810 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": 1104619, "vin": [ { "gen": { "height": 1104609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8b6b9d494d1980fb73b6384914fbb6356e978a9e6195a8c9556df9a1ed1713d" } } ], "extra": [ 1, 55, 133, 17, 250, 180, 250, 41, 163, 229, 59, 201, 78, 152, 117, 151, 27, 200, 147, 180, 46, 133, 7, 37, 242, 96, 25, 174, 216, 34, 211, 131, 203, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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