Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d75fbaae2035173dd8661c12dccecf6ad30191fd5597acaac3c82c28f1c801e9

Tx prefix hash: 4d5d53d0ce9069399e862ea4e984f46b3454f62ee05e7b878e28e52ef6718be9
Tx public key: e935bca5aceca47ed957c00b1890faa0a7f59f4faf53de03453303d1c375e9e0
Timestamp: 1708662540 Timestamp [UCT]: 2024-02-23 04:29:00 Age [y:d:h:m:s]: 01:046:15:56:29
Block: 963562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294365 RingCT/type: yes/0
Extra: 01e935bca5aceca47ed957c00b1890faa0a7f59f4faf53de03453303d1c375e9e002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c295f58a18810781b8f3da3780df891bf0854b1ca0e145c929990d0bce45d2b1 0.600000000000 1423277 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": 963572, "vin": [ { "gen": { "height": 963562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c295f58a18810781b8f3da3780df891bf0854b1ca0e145c929990d0bce45d2b1" } } ], "extra": [ 1, 233, 53, 188, 165, 172, 236, 164, 126, 217, 87, 192, 11, 24, 144, 250, 160, 167, 245, 159, 79, 175, 83, 222, 3, 69, 51, 3, 209, 195, 117, 233, 224, 2, 17, 0, 0, 0, 1, 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