Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caa222743683c4a938a91c177bb7bd5552985ae8fe3688dd45e5ca547b4fd7d2

Tx prefix hash: eba7ae439b1edaf7e7e8f1daff4f7870b68c8cdefb804d95bf8822fbc4e4f3dc
Tx public key: 9632b90f79bcacc6f5c245213dddcff5fbcd64c938498c081fe5506bcfcb316d
Timestamp: 1765737259 Timestamp [UCT]: 2025-12-14 18:34:19 Age [y:d:h:m:s]: 00:002:11:03:46
Block: 1433597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1766 RingCT/type: yes/0
Extra: 019632b90f79bcacc6f5c245213dddcff5fbcd64c938498c081fe5506bcfcb316d0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ba6ba313ed2a9865f9718eab02e15a46642c0ceabf98d64aa768c3ef8bc421d 0.600000000000 1922378 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": 1433607, "vin": [ { "gen": { "height": 1433597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ba6ba313ed2a9865f9718eab02e15a46642c0ceabf98d64aa768c3ef8bc421d" } } ], "extra": [ 1, 150, 50, 185, 15, 121, 188, 172, 198, 245, 194, 69, 33, 61, 221, 207, 245, 251, 205, 100, 201, 56, 73, 140, 8, 31, 229, 80, 107, 207, 203, 49, 109, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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