Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c271d95214061b4a44ecc306c59aa2b2e43a66fd13bbeff4e11b73feca7c21f8

Tx prefix hash: 40be77df54e7fcee9492c3388ead10d4cc4f27fe97efa74f1ba24fa3e2fc23c2
Tx public key: 0d10d05c02f41a235547bd1dd40802a58f1207188cdec8b758aee56137931db3
Timestamp: 1700810908 Timestamp [UCT]: 2023-11-24 07:28:28 Age [y:d:h:m:s]: 01:135:01:58:24
Block: 898464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357708 RingCT/type: yes/0
Extra: 010d10d05c02f41a235547bd1dd40802a58f1207188cdec8b758aee56137931db3021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.647166135000 dcy

stealth address amount amount idx
00: d7b39c8dff8f09bc132f189b10a548b13d631e4b82efce54afc90f5da0511359 0.647166135000 1354881 of 0

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": 898474, "vin": [ { "gen": { "height": 898464 } } ], "vout": [ { "amount": 647166135, "target": { "key": "d7b39c8dff8f09bc132f189b10a548b13d631e4b82efce54afc90f5da0511359" } } ], "extra": [ 1, 13, 16, 208, 92, 2, 244, 26, 35, 85, 71, 189, 29, 212, 8, 2, 165, 143, 18, 7, 24, 140, 222, 200, 183, 88, 174, 229, 97, 55, 147, 29, 179, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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