Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8b9f5a321a428386c1b3947e4f3918e9ec220108f8cd44d6f1efea8999f7f20

Tx prefix hash: 7fa6fc0839bc65bb97109878f50bc23a4fccf54f4f8c866ec9751ba43b8459d4
Tx public key: c1e99533cc8a5fde58e405cb09676f2fe0becc9f7a1d80770f6e4bf34b69781a
Timestamp: 1727250956 Timestamp [UCT]: 2024-09-25 07:55:56 Age [y:d:h:m:s]: 00:119:15:06:39
Block: 1117664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85501 RingCT/type: yes/0
Extra: 01c1e99533cc8a5fde58e405cb09676f2fe0becc9f7a1d80770f6e4bf34b69781a02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d29ba49d996bfe91142417f34e243976f1773bd4a5167d8f25cc609d4c1687ff 0.600000000000 1598587 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": 1117674, "vin": [ { "gen": { "height": 1117664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d29ba49d996bfe91142417f34e243976f1773bd4a5167d8f25cc609d4c1687ff" } } ], "extra": [ 1, 193, 233, 149, 51, 204, 138, 95, 222, 88, 228, 5, 203, 9, 103, 111, 47, 224, 190, 204, 159, 122, 29, 128, 119, 15, 110, 75, 243, 75, 105, 120, 26, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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