Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d1eed42dda444fad6e28829a14f4256d3fd3cfacf71028a5965a7f1af8a6533

Tx prefix hash: cf6f83f38d3872cdd165f95b011cb3c18f15b9dfc91e6ac8cf9d9d7405f80e2c
Tx public key: 41666f18fcc85e6324c248a962b523615049465e0841a16044300bf18f1b0133
Timestamp: 1707671631 Timestamp [UCT]: 2024-02-11 17:13:51 Age [y:d:h:m:s]: 01:120:06:05:41
Block: 955344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347034 RingCT/type: yes/0
Extra: 0141666f18fcc85e6324c248a962b523615049465e0841a16044300bf18f1b01330211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d366bcdc0ea8f19bd9cb8273eb0093385a42f3118b1b4a9e43c73f0da2b00bb 0.600000000000 1414632 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": 955354, "vin": [ { "gen": { "height": 955344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d366bcdc0ea8f19bd9cb8273eb0093385a42f3118b1b4a9e43c73f0da2b00bb" } } ], "extra": [ 1, 65, 102, 111, 24, 252, 200, 94, 99, 36, 194, 72, 169, 98, 181, 35, 97, 80, 73, 70, 94, 8, 65, 161, 96, 68, 48, 11, 241, 143, 27, 1, 51, 2, 17, 0, 0, 0, 4, 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