Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2913dd905e0218df9c8c6dabe88b87322df8c18054d315f78b4284936efb8b3d

Tx prefix hash: fd38d47171247b1a45f64c7eca8a604fae53111e9d3a9779352e54af28eac376
Tx public key: faa557a18e3e05f0ae02b9d89d546aa739a2a0fe3b82d570ff0db1bec0c62564
Timestamp: 1761997178 Timestamp [UCT]: 2025-11-01 11:39:38 Age [y:d:h:m:s]: 00:006:23:42:46
Block: 1402638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4970 RingCT/type: yes/0
Extra: 01faa557a18e3e05f0ae02b9d89d546aa739a2a0fe3b82d570ff0db1bec0c62564021100000013df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91fe5ce7420e0d2d5048b230acc43f538d706870c6e2be216e011c686124b7f4 0.600000000000 1890957 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": 1402648, "vin": [ { "gen": { "height": 1402638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91fe5ce7420e0d2d5048b230acc43f538d706870c6e2be216e011c686124b7f4" } } ], "extra": [ 1, 250, 165, 87, 161, 142, 62, 5, 240, 174, 2, 185, 216, 157, 84, 106, 167, 57, 162, 160, 254, 59, 130, 213, 112, 255, 13, 177, 190, 192, 198, 37, 100, 2, 17, 0, 0, 0, 19, 223, 90, 36, 122, 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