Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c42005e129e641ffb2fb47f64bd37b546bb6b217574638e460fba43cc54e7d6d

Tx prefix hash: 98e951c42317fb9cdc4818c08a7f10d6cd359d5cd58628aab74cb0bf17c53451
Tx public key: 5679be5d7dbfd5a4878096e025fdb2d681135b2227eb0d261329e62881a15cf5
Timestamp: 1736350571 Timestamp [UCT]: 2025-01-08 15:36:11 Age [y:d:h:m:s]: 00:126:02:07:51
Block: 1192965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89941 RingCT/type: yes/0
Extra: 015679be5d7dbfd5a4878096e025fdb2d681135b2227eb0d261329e62881a15cf5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60d76854fd5f48c89475ffd5d766899c9b9b5aac1d99887780e3a1b036cf4024 0.600000000000 1679522 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": 1192975, "vin": [ { "gen": { "height": 1192965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60d76854fd5f48c89475ffd5d766899c9b9b5aac1d99887780e3a1b036cf4024" } } ], "extra": [ 1, 86, 121, 190, 93, 125, 191, 213, 164, 135, 128, 150, 224, 37, 253, 178, 214, 129, 19, 91, 34, 39, 235, 13, 38, 19, 41, 230, 40, 129, 161, 92, 245, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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