Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 770f99ac3ab2bd150db0134a6cda3b3334768ef3a855e63dd7251a2a7ff87d9e

Tx prefix hash: 9ee78d5b00ea2fda816efc43b50f825516121452f7f786903da3fe8dd4e6dbee
Tx public key: da8388ff353069c60f87c2ed106c555c1641fb7af0ae07c868ceb0b24ee0e620
Timestamp: 1720112109 Timestamp [UCT]: 2024-07-04 16:55:09 Age [y:d:h:m:s]: 00:205:14:57:00
Block: 1058478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147099 RingCT/type: yes/0
Extra: 01da8388ff353069c60f87c2ed106c555c1641fb7af0ae07c868ceb0b24ee0e6200211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e45874577809a765df10d38c013f41dc76fd85f52742517b243c0e193eef170 0.600000000000 1528935 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": 1058488, "vin": [ { "gen": { "height": 1058478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e45874577809a765df10d38c013f41dc76fd85f52742517b243c0e193eef170" } } ], "extra": [ 1, 218, 131, 136, 255, 53, 48, 105, 198, 15, 135, 194, 237, 16, 108, 85, 92, 22, 65, 251, 122, 240, 174, 7, 200, 104, 206, 176, 178, 78, 224, 230, 32, 2, 17, 0, 0, 0, 7, 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