Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 746bc3c28c37eba04a36d01d8fd68febc2e99b5305f3f197ebc1ab114745c937

Tx prefix hash: fa687c14ee6855456144d6bf572452c897c294574350d6ea4638723e25a3748a
Tx public key: 0c2788a91414c49f862974ce7a1a46ee622e3f0c2fcac3c6e58fbbda1e47bce6
Timestamp: 1679714830 Timestamp [UCT]: 2023-03-25 03:27:10 Age [y:d:h:m:s]: 02:016:23:58:35
Block: 724466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533683 RingCT/type: yes/0
Extra: 010c2788a91414c49f862974ce7a1a46ee622e3f0c2fcac3c6e58fbbda1e47bce6021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.440862298000 dcy

stealth address amount amount idx
00: 865a05b0fb9d9d8a6d9c09ac7d8111ce7cb0603ba94b18fd8cf451d5a9211a12 2.440862298000 1169489 of 0

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": 724476, "vin": [ { "gen": { "height": 724466 } } ], "vout": [ { "amount": 2440862298, "target": { "key": "865a05b0fb9d9d8a6d9c09ac7d8111ce7cb0603ba94b18fd8cf451d5a9211a12" } } ], "extra": [ 1, 12, 39, 136, 169, 20, 20, 196, 159, 134, 41, 116, 206, 122, 26, 70, 238, 98, 46, 63, 12, 47, 202, 195, 198, 229, 143, 187, 218, 30, 71, 188, 230, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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