Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 399c6305feae3204d1ba3e76dfee274e775602b84d6d0d702aa3f807b827b12e

Tx prefix hash: 311ed12738de2b28d8a4fc9626b6855daef234e4325a61c1c4776b5189ab6021
Tx public key: 01cd07e3f7ae7791738544686abfdabaa8bed272644c5b2d6ef3b1054bf5aa92
Timestamp: 1710711968 Timestamp [UCT]: 2024-03-17 21:46:08 Age [y:d:h:m:s]: 01:084:00:00:35
Block: 980571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321053 RingCT/type: yes/0
Extra: 0101cd07e3f7ae7791738544686abfdabaa8bed272644c5b2d6ef3b1054bf5aa920211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0844c9a11cdc21a9d19001c40a190e979f09be481c21c2e8af831f439a31f909 0.600000000000 1440646 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": 980581, "vin": [ { "gen": { "height": 980571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0844c9a11cdc21a9d19001c40a190e979f09be481c21c2e8af831f439a31f909" } } ], "extra": [ 1, 1, 205, 7, 227, 247, 174, 119, 145, 115, 133, 68, 104, 106, 191, 218, 186, 168, 190, 210, 114, 100, 76, 91, 45, 110, 243, 177, 5, 75, 245, 170, 146, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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