Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7b9a1ab727c1775e36d4d842d48c77593c44b31ec6cdba8f91e37355608b51

Tx prefix hash: 5a84b6107baa925f0b9fa9c806826dd2f01ff603bb7af4f2903af94b794747ea
Tx public key: e48c436cb9a02189599b35a7e9a8fc716606a659414b103c269ac1d47163ebd6
Timestamp: 1717304151 Timestamp [UCT]: 2024-06-02 04:55:51 Age [y:d:h:m:s]: 00:286:18:25:25
Block: 1035211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204963 RingCT/type: yes/0
Extra: 01e48c436cb9a02189599b35a7e9a8fc716606a659414b103c269ac1d47163ebd602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cffb12908cdd1e478ef15ecf6733d6dd6dd8cd66be07994abcf1a51c41598d2 0.600000000000 1503732 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": 1035221, "vin": [ { "gen": { "height": 1035211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cffb12908cdd1e478ef15ecf6733d6dd6dd8cd66be07994abcf1a51c41598d2" } } ], "extra": [ 1, 228, 140, 67, 108, 185, 160, 33, 137, 89, 155, 53, 167, 233, 168, 252, 113, 102, 6, 166, 89, 65, 75, 16, 60, 38, 154, 193, 212, 113, 99, 235, 214, 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