Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42075bff01e6b1bb8131cbb97bb60b79242994eb4f1dcc34f72e2d9ab8415a34

Tx prefix hash: 11f0b795a2890765f160b3855b25f278faac4246d1cae88946077e70ac31b1ea
Tx public key: 875d74410edafce61effa5baf0bf40d6fab2104335fff9e418c2f52c3fddd23c
Timestamp: 1750601571 Timestamp [UCT]: 2025-06-22 14:12:51 Age [y:d:h:m:s]: 00:152:09:49:01
Block: 1310498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106796 RingCT/type: yes/0
Extra: 01875d74410edafce61effa5baf0bf40d6fab2104335fff9e418c2f52c3fddd23c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e74c7bfc7cb4bdc0dedeebe0ed32dec7b86c6747f325dad0f95e7d1a9fb67f5 0.600000000000 1798119 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": 1310508, "vin": [ { "gen": { "height": 1310498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e74c7bfc7cb4bdc0dedeebe0ed32dec7b86c6747f325dad0f95e7d1a9fb67f5" } } ], "extra": [ 1, 135, 93, 116, 65, 14, 218, 252, 230, 30, 255, 165, 186, 240, 191, 64, 214, 250, 178, 16, 67, 53, 255, 249, 228, 24, 194, 245, 44, 63, 221, 210, 60, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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