Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b277b4d51c7cd96f48cb58a4055c34356b26a25ebd80c4be36b26f5764930369

Tx prefix hash: f5ba44bff13a483d81bb8cb9971821903fb1b631293656069ee0d11221586c5f
Tx public key: cd205d79674bf04cec53db80dc0e28ad5a73fda9b387d4aecf6ae6f2ef1b9d5d
Timestamp: 1763896293 Timestamp [UCT]: 2025-11-23 11:11:33 Age [y:d:h:m:s]: 00:003:21:42:51
Block: 1418346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2805 RingCT/type: yes/0
Extra: 01cd205d79674bf04cec53db80dc0e28ad5a73fda9b387d4aecf6ae6f2ef1b9d5d0211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c2bd1c35169b6034e7ada586967bb5e436cd4bc817897bcf9d9a662b44da3ae 0.600000000000 1906877 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": 1418356, "vin": [ { "gen": { "height": 1418346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c2bd1c35169b6034e7ada586967bb5e436cd4bc817897bcf9d9a662b44da3ae" } } ], "extra": [ 1, 205, 32, 93, 121, 103, 75, 240, 76, 236, 83, 219, 128, 220, 14, 40, 173, 90, 115, 253, 169, 179, 135, 212, 174, 207, 106, 230, 242, 239, 27, 157, 93, 2, 17, 0, 0, 0, 1, 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