Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38a7a4968b6bd1d6fae60aad3e04d6c8c30464c09d008dabf6b66a7d87d097a2

Tx prefix hash: 536d1ea73e732e4ff6806c373345acc82bd396ae5b15abc5fa06fa1ae7fbb300
Tx public key: 589af74e228b79a79c08ca81ebce032edbe1e2f9906fc6f7e7f53ef3d66413e9
Timestamp: 1697844605 Timestamp [UCT]: 2023-10-20 23:30:05 Age [y:d:h:m:s]: 01:095:04:00:09
Block: 874074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329225 RingCT/type: yes/0
Extra: 01589af74e228b79a79c08ca81ebce032edbe1e2f9906fc6f7e7f53ef3d66413e902110000000733af99f4000000000000000000

1 output(s) for total of 0.779524939000 dcy

stealth address amount amount idx
00: 3b9d612cb1de7d23bf341fbe9f34424f2a3ff824f2f564eb52f930e0e2435ec8 0.779524939000 1329268 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": 874084, "vin": [ { "gen": { "height": 874074 } } ], "vout": [ { "amount": 779524939, "target": { "key": "3b9d612cb1de7d23bf341fbe9f34424f2a3ff824f2f564eb52f930e0e2435ec8" } } ], "extra": [ 1, 88, 154, 247, 78, 34, 139, 121, 167, 156, 8, 202, 129, 235, 206, 3, 46, 219, 225, 226, 249, 144, 111, 198, 247, 231, 245, 62, 243, 214, 100, 19, 233, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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