Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f3415f0c68f26eab9eff5dbc2d135482e1407519af22f1ef301716137187de4

Tx prefix hash: 6ebee04a87591e3ff9177d3767c9bb3834b187fee5b6d0bb368078d61b3a4ad1
Tx public key: 3c65c2140d0ed79ae3c3e516fa27fb640ed0db14c7bfd55f87212faaaaa78f6b
Timestamp: 1708735299 Timestamp [UCT]: 2024-02-24 00:41:39 Age [y:d:h:m:s]: 01:118:10:10:54
Block: 964170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345535 RingCT/type: yes/0
Extra: 013c65c2140d0ed79ae3c3e516fa27fb640ed0db14c7bfd55f87212faaaaa78f6b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 302ca423bc5042b40aaf2893fbba6dca06673bb6e9f2bd1609104d1ddd8c45db 0.600000000000 1423897 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": 964180, "vin": [ { "gen": { "height": 964170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "302ca423bc5042b40aaf2893fbba6dca06673bb6e9f2bd1609104d1ddd8c45db" } } ], "extra": [ 1, 60, 101, 194, 20, 13, 14, 215, 154, 227, 195, 229, 22, 250, 39, 251, 100, 14, 208, 219, 20, 199, 191, 213, 95, 135, 33, 47, 170, 170, 167, 143, 107, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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