Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d4a580be77cc6fe8d019e8997597d083f757cd1fcbd0e924e278d09c7c0467

Tx prefix hash: 82e65afe05f8c78313e393441200f9d0ecec311162ad276a9291fadfb7c17255
Tx public key: a65ce9c3f34f6ed36d1e6daa9f9c21c730ba70c313aee3dfc59ab39afc28eda6
Timestamp: 1705756295 Timestamp [UCT]: 2024-01-20 13:11:35 Age [y:d:h:m:s]: 01:103:01:33:51
Block: 939435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334784 RingCT/type: yes/0
Extra: 01a65ce9c3f34f6ed36d1e6daa9f9c21c730ba70c313aee3dfc59ab39afc28eda60211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a7625b340ac0b1909305e6e7fa911582a5eb6cc2e562b3476737b125c4277b4 0.600000000000 1397543 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": 939445, "vin": [ { "gen": { "height": 939435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a7625b340ac0b1909305e6e7fa911582a5eb6cc2e562b3476737b125c4277b4" } } ], "extra": [ 1, 166, 92, 233, 195, 243, 79, 110, 211, 109, 30, 109, 170, 159, 156, 33, 199, 48, 186, 112, 195, 19, 174, 227, 223, 197, 154, 179, 154, 252, 40, 237, 166, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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