Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ecd97e1bb48fc88cc03135560b40b9c7b028b674c441c836a90e867fc1ea1bd

Tx prefix hash: b45b0e3a389db6d389eab58da473d98cb14de0bae1cddb92a470881ef9c83dc0
Tx public key: 1ddbd22afd272f6e10e5888d7082e114bcc8e7cd0c61f213b00f572ed45e1104
Timestamp: 1754648126 Timestamp [UCT]: 2025-08-08 10:15:26 Age [y:d:h:m:s]: 00:105:07:04:20
Block: 1342740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74350 RingCT/type: yes/0
Extra: 011ddbd22afd272f6e10e5888d7082e114bcc8e7cd0c61f213b00f572ed45e110402110000000bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48fc88208fcd4e8b24d00c651b7ebc30ca93f9c34737b5b075a12b74c09a9ee9 0.600000000000 1830573 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": 1342750, "vin": [ { "gen": { "height": 1342740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48fc88208fcd4e8b24d00c651b7ebc30ca93f9c34737b5b075a12b74c09a9ee9" } } ], "extra": [ 1, 29, 219, 210, 42, 253, 39, 47, 110, 16, 229, 136, 141, 112, 130, 225, 20, 188, 200, 231, 205, 12, 97, 242, 19, 176, 15, 87, 46, 212, 94, 17, 4, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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