Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2085c50833d94e50d69866f770686153b34a112c2bde5e102b017b0e8a802b2e

Tx prefix hash: 4d7b0fc166fe49309a2f05141c018dfc869adfb76c05376fe4013592d85461d4
Tx public key: 3a3a0d352c712f9881171468697f8b301bca41b8d4f516935487f83d218a1d6e
Timestamp: 1739331790 Timestamp [UCT]: 2025-02-12 03:43:10 Age [y:d:h:m:s]: 00:329:09:54:34
Block: 1217389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233259 RingCT/type: yes/0
Extra: 013a3a0d352c712f9881171468697f8b301bca41b8d4f516935487f83d218a1d6e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d144b21e402897c314b665c783a595683284d3088e477613a2d47309c58f9a4d 0.600000000000 1704198 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": 1217399, "vin": [ { "gen": { "height": 1217389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d144b21e402897c314b665c783a595683284d3088e477613a2d47309c58f9a4d" } } ], "extra": [ 1, 58, 58, 13, 53, 44, 113, 47, 152, 129, 23, 20, 104, 105, 127, 139, 48, 27, 202, 65, 184, 212, 245, 22, 147, 84, 135, 248, 61, 33, 138, 29, 110, 2, 17, 0, 0, 0, 1, 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