Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fc774025dc285c2d425010fe420607a696dda7c7cd5c31bc6364d7d3ff1e5af

Tx prefix hash: 905cf1c123571fd3d6861df20eabc469288074729a7554c74cb3e853582aeff8
Tx public key: 1fd3679ea78e1a45380a67299f06c760b25a85fd0c221dd11f23fb3acc09a304
Timestamp: 1764274413 Timestamp [UCT]: 2025-11-27 20:13:33 Age [y:d:h:m:s]: 00:038:23:52:58
Block: 1421488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27931 RingCT/type: yes/0
Extra: 011fd3679ea78e1a45380a67299f06c760b25a85fd0c221dd11f23fb3acc09a3040211000000038ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a814f5bb478c34901e25ae5f35202a872b23f0e96362aa44a551b13f5131cf96 0.600000000000 1910045 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": 1421498, "vin": [ { "gen": { "height": 1421488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a814f5bb478c34901e25ae5f35202a872b23f0e96362aa44a551b13f5131cf96" } } ], "extra": [ 1, 31, 211, 103, 158, 167, 142, 26, 69, 56, 10, 103, 41, 159, 6, 199, 96, 178, 90, 133, 253, 12, 34, 29, 209, 31, 35, 251, 58, 204, 9, 163, 4, 2, 17, 0, 0, 0, 3, 140, 235, 127, 9, 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