Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e574713e2a98ff7201bbaf3ddb4b1273617bb78cfb47ebc22cbb8c3106eb27

Tx prefix hash: 9691fd5f1060a42062ee03e584a7547000ca9292464180329c2742e4abf69c7f
Tx public key: 8fc2f08c0b75b4d7cbb9a35e70993fb5cfdaf7f10ff914ddb336f7bd9a045972
Timestamp: 1759398320 Timestamp [UCT]: 2025-10-02 09:45:20 Age [y:d:h:m:s]: 00:048:22:37:43
Block: 1381064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35050 RingCT/type: yes/0
Extra: 018fc2f08c0b75b4d7cbb9a35e70993fb5cfdaf7f10ff914ddb336f7bd9a04597202110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc365f7e04411d1839a4c192ee5fb96b5d9abe149974fd5d7ee16620e3a705c 0.600000000000 1869177 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": 1381074, "vin": [ { "gen": { "height": 1381064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc365f7e04411d1839a4c192ee5fb96b5d9abe149974fd5d7ee16620e3a705c" } } ], "extra": [ 1, 143, 194, 240, 140, 11, 117, 180, 215, 203, 185, 163, 94, 112, 153, 63, 181, 207, 218, 247, 241, 15, 249, 20, 221, 179, 54, 247, 189, 154, 4, 89, 114, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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