Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc2f27a19147bea34fada5cebc4863917df6193ba92fb85bd0a8984f99b999d

Tx prefix hash: 1a6fef6d72fdbc7669de7923385d47db3c659c0e8a092890374bbd299955ea0b
Tx public key: 9e6f961d5d633582414f96cf3d092992233868e93e2bc0eb245ccc0d8e97d59b
Timestamp: 1735246118 Timestamp [UCT]: 2024-12-26 20:48:38 Age [y:d:h:m:s]: 00:083:01:24:28
Block: 1183830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59166 RingCT/type: yes/0
Extra: 019e6f961d5d633582414f96cf3d092992233868e93e2bc0eb245ccc0d8e97d59b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d73d6f1f551f1f087525facb122be49d67e23df678be192a58540d47a6f2b3d 0.600000000000 1670279 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": 1183840, "vin": [ { "gen": { "height": 1183830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d73d6f1f551f1f087525facb122be49d67e23df678be192a58540d47a6f2b3d" } } ], "extra": [ 1, 158, 111, 150, 29, 93, 99, 53, 130, 65, 79, 150, 207, 61, 9, 41, 146, 35, 56, 104, 233, 62, 43, 192, 235, 36, 92, 204, 13, 142, 151, 213, 155, 2, 17, 0, 0, 0, 7, 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