Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32af0c8d2d2a4327a035ff8213a73bd353ce69ab7e29579b156bc17f3b96379d

Tx prefix hash: e9853eb2a39630dc254c304a16c1512a26774ad0fa042b9fb747aa2527745972
Tx public key: 608c85bbb8b18b78ff55248a37b68f98d1a5227307c49e6c18239c5fd6ce87d9
Timestamp: 1696114907 Timestamp [UCT]: 2023-09-30 23:01:47 Age [y:d:h:m:s]: 01:121:00:07:25
Block: 859738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347512 RingCT/type: yes/0
Extra: 01608c85bbb8b18b78ff55248a37b68f98d1a5227307c49e6c18239c5fd6ce87d902110000000333af99f4000000000000000000

1 output(s) for total of 0.869623273000 dcy

stealth address amount amount idx
00: 6290bc68d8310d6026c537c1012960a7741f989879ba2d5e24ed80973b8083a2 0.869623273000 1313980 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": 859748, "vin": [ { "gen": { "height": 859738 } } ], "vout": [ { "amount": 869623273, "target": { "key": "6290bc68d8310d6026c537c1012960a7741f989879ba2d5e24ed80973b8083a2" } } ], "extra": [ 1, 96, 140, 133, 187, 184, 177, 139, 120, 255, 85, 36, 138, 55, 182, 143, 152, 209, 165, 34, 115, 7, 196, 158, 108, 24, 35, 156, 95, 214, 206, 135, 217, 2, 17, 0, 0, 0, 3, 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