Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd6b5f4f2f6593c535810592a2ded5ac4f123caa8489032508df0e78f3f5291

Tx prefix hash: f6b9a32c16142d4373b8c18e0293e49665bdb4b2d7fbf5bd7f9a9ccdfaf7fe12
Tx public key: 783a01aa3d9567b4205e6b8691d71a70b4ddd387f9d3fbf4ab0489fde72f9e89
Timestamp: 1737202057 Timestamp [UCT]: 2025-01-18 12:07:37 Age [y:d:h:m:s]: 00:153:16:40:27
Block: 1200017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109506 RingCT/type: yes/0
Extra: 01783a01aa3d9567b4205e6b8691d71a70b4ddd387f9d3fbf4ab0489fde72f9e890211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 915ead3f73bd46a6dfe2011080cdcc3a9441caf5fa6e4fbe7a740d8ba0d05083 0.600000000000 1686658 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": 1200027, "vin": [ { "gen": { "height": 1200017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "915ead3f73bd46a6dfe2011080cdcc3a9441caf5fa6e4fbe7a740d8ba0d05083" } } ], "extra": [ 1, 120, 58, 1, 170, 61, 149, 103, 180, 32, 94, 107, 134, 145, 215, 26, 112, 180, 221, 211, 135, 249, 211, 251, 244, 171, 4, 137, 253, 231, 47, 158, 137, 2, 17, 0, 0, 0, 4, 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