Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fe67fe24e8811077a1c769b223d7c6ad992f06657f303e6d4dbe8f6108b2240

Tx prefix hash: 88c1f44d9dd07865eac39382244d4f5b3cc8389fd86b97e641915051d5ddf556
Tx public key: ffb4ecef3b809478d0e5b09903c9e0fb2262e7bd4758c995800f93a2d59df8e5
Timestamp: 1748183401 Timestamp [UCT]: 2025-05-25 14:30:01 Age [y:d:h:m:s]: 00:212:10:21:13
Block: 1290677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149553 RingCT/type: yes/0
Extra: 01ffb4ecef3b809478d0e5b09903c9e0fb2262e7bd4758c995800f93a2d59df8e5021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54ad2f2361771aab58644fbacd9c34cecf641db3cf2f0de858c8c4160c3b6475 0.600000000000 1778146 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": 1290687, "vin": [ { "gen": { "height": 1290677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54ad2f2361771aab58644fbacd9c34cecf641db3cf2f0de858c8c4160c3b6475" } } ], "extra": [ 1, 255, 180, 236, 239, 59, 128, 148, 120, 208, 229, 176, 153, 3, 201, 224, 251, 34, 98, 231, 189, 71, 88, 201, 149, 128, 15, 147, 162, 213, 157, 248, 229, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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