Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa38265800f686f7cfbf7c35c659c8b350851be8f4262afe78f75592d9ef40a

Tx prefix hash: 094f199dd0d5ad90a55963aafdb3cf18bfa28fc693e45fe85cecc8f9315d275b
Tx public key: 8ee7b6205a882ed9ed5cbdee259e40f434a44c2fd962a412a17618bbe5afd2f0
Timestamp: 1742649405 Timestamp [UCT]: 2025-03-22 13:16:45 Age [y:d:h:m:s]: 00:244:04:34:06
Block: 1244854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172251 RingCT/type: yes/0
Extra: 018ee7b6205a882ed9ed5cbdee259e40f434a44c2fd962a412a17618bbe5afd2f0021100000008af845649000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6628dae1bc4af20dca5a6cb8041dcb9817af87f5037fe3a04a13ef3bf9889b11 0.600000000000 1731845 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": 1244864, "vin": [ { "gen": { "height": 1244854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6628dae1bc4af20dca5a6cb8041dcb9817af87f5037fe3a04a13ef3bf9889b11" } } ], "extra": [ 1, 142, 231, 182, 32, 90, 136, 46, 217, 237, 92, 189, 238, 37, 158, 64, 244, 52, 164, 76, 47, 217, 98, 164, 18, 161, 118, 24, 187, 229, 175, 210, 240, 2, 17, 0, 0, 0, 8, 175, 132, 86, 73, 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