Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97257d5e5b42a3291d0ce1e4f43467fd3c2532209410791f4bfecbec47b0aaf7

Tx prefix hash: dd57f10a55bd771f83a86aa52380ead1085170574f41502af706c38b9923ffe7
Tx public key: 87074d610cfa811198e028f435b7e6467da588c83b904be0f086646574af44f7
Timestamp: 1696881769 Timestamp [UCT]: 2023-10-09 20:02:49 Age [y:d:h:m:s]: 01:141:16:39:15
Block: 866104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362278 RingCT/type: yes/0
Extra: 0187074d610cfa811198e028f435b7e6467da588c83b904be0f086646574af44f7021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.828395906000 dcy

stealth address amount amount idx
00: b62f8e3f2f5936f24c29adc1bc861849bd96b8ef46b209de0b2fe42e99d81fc8 0.828395906000 1320672 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": 866114, "vin": [ { "gen": { "height": 866104 } } ], "vout": [ { "amount": 828395906, "target": { "key": "b62f8e3f2f5936f24c29adc1bc861849bd96b8ef46b209de0b2fe42e99d81fc8" } } ], "extra": [ 1, 135, 7, 77, 97, 12, 250, 129, 17, 152, 224, 40, 244, 53, 183, 230, 70, 125, 165, 136, 200, 59, 144, 75, 224, 240, 134, 100, 101, 116, 175, 68, 247, 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