Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41fb8438a5364ace3b286bce733b104a1e0b100222df9886338dc265972762f6

Tx prefix hash: f9b45be48fe1a5e57e08e33688b965507107b2be8bb848c87545ccb679c3eb6c
Tx public key: e996ea54b267a001935295d93a94cc5a07506b8d2b28e694b450bdb57400fa55
Timestamp: 1696379561 Timestamp [UCT]: 2023-10-04 00:32:41 Age [y:d:h:m:s]: 01:190:03:12:50
Block: 861930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396942 RingCT/type: yes/0
Extra: 01e996ea54b267a001935295d93a94cc5a07506b8d2b28e694b450bdb57400fa5502110000000675e3f0e9000000000000000000

1 output(s) for total of 0.855200892000 dcy

stealth address amount amount idx
00: 3abe893b5605c1596dc9c8311388a508a6dd6982dd063732a7d9d887d942b7e2 0.855200892000 1316310 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": 861940, "vin": [ { "gen": { "height": 861930 } } ], "vout": [ { "amount": 855200892, "target": { "key": "3abe893b5605c1596dc9c8311388a508a6dd6982dd063732a7d9d887d942b7e2" } } ], "extra": [ 1, 233, 150, 234, 84, 178, 103, 160, 1, 147, 82, 149, 217, 58, 148, 204, 90, 7, 80, 107, 141, 43, 40, 230, 148, 180, 80, 189, 181, 116, 0, 250, 85, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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