Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd39bd5a6a34860b724b479835b7e22b5fc143e296526a71342b4273935b6258

Tx prefix hash: c7854f206347234c109c8b2cf32ad92f83e81f920a2f5469aac8f3dc5080f7cd
Tx public key: 465f79d9c4973bd6bb25fb748523f3a2b17bb0bf724d11a41049471c5be13207
Timestamp: 1704215879 Timestamp [UCT]: 2024-01-02 17:17:59 Age [y:d:h:m:s]: 01:337:02:57:34
Block: 926686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499825 RingCT/type: yes/0
Extra: 01465f79d9c4973bd6bb25fb748523f3a2b17bb0bf724d11a41049471c5be132070211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 468d09158a0a3bf9bb9fb73fe2929f9de35710a9b75c3dc1d025ed5930c93e75 0.600000000000 1384482 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": 926696, "vin": [ { "gen": { "height": 926686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "468d09158a0a3bf9bb9fb73fe2929f9de35710a9b75c3dc1d025ed5930c93e75" } } ], "extra": [ 1, 70, 95, 121, 217, 196, 151, 59, 214, 187, 37, 251, 116, 133, 35, 243, 162, 177, 123, 176, 191, 114, 77, 17, 164, 16, 73, 71, 28, 91, 225, 50, 7, 2, 17, 0, 0, 0, 2, 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