Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c9c18c88e99d0464d353fee5784c27925dcfe1624b39c766e36fff9a8eedc6

Tx prefix hash: 7a4428997dfa0e8f2ae8f6795967ecde53fd2f7209c7a56f6b868cb4467df914
Tx public key: 92d76e7a5cdb9b638772916167917828de66e585201cc4a222e6f7a9b3996a29
Timestamp: 1753562468 Timestamp [UCT]: 2025-07-26 20:41:08 Age [y:d:h:m:s]: 00:124:03:12:19
Block: 1334033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87563 RingCT/type: yes/0
Extra: 0192d76e7a5cdb9b638772916167917828de66e585201cc4a222e6f7a9b3996a29021100000001ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d57cc9ffc01e3c2256db6c0fe5d69239ea2363de2599a54b2ff12fda4dc19b9d 0.600000000000 1821832 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": 1334043, "vin": [ { "gen": { "height": 1334033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d57cc9ffc01e3c2256db6c0fe5d69239ea2363de2599a54b2ff12fda4dc19b9d" } } ], "extra": [ 1, 146, 215, 110, 122, 92, 219, 155, 99, 135, 114, 145, 97, 103, 145, 120, 40, 222, 102, 229, 133, 32, 28, 196, 162, 34, 230, 247, 169, 179, 153, 106, 41, 2, 17, 0, 0, 0, 1, 239, 34, 20, 133, 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