Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f8d3bca3271e79c4735e63413932fea98a11c3d5c2c18e4491c8c0d5c066db

Tx prefix hash: 651ac9285d1ea7bd973653b275ad7ad90bce606658d4652bda232a724d38f78f
Tx public key: 439ca3bee579fff9b90e28ccd5ff542552f5da41dca4b2a740997283054d5cb9
Timestamp: 1696145615 Timestamp [UCT]: 2023-10-01 07:33:35 Age [y:d:h:m:s]: 01:187:20:16:01
Block: 859998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395294 RingCT/type: yes/0
Extra: 01439ca3bee579fff9b90e28ccd5ff542552f5da41dca4b2a740997283054d5cb9021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.867899955000 dcy

stealth address amount amount idx
00: f879ddb392e944212dc21c271c3da001cb2add816527d630fc28650351e6a106 0.867899955000 1314256 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": 860008, "vin": [ { "gen": { "height": 859998 } } ], "vout": [ { "amount": 867899955, "target": { "key": "f879ddb392e944212dc21c271c3da001cb2add816527d630fc28650351e6a106" } } ], "extra": [ 1, 67, 156, 163, 190, 229, 121, 255, 249, 185, 14, 40, 204, 213, 255, 84, 37, 82, 245, 218, 65, 220, 164, 178, 167, 64, 153, 114, 131, 5, 77, 92, 185, 2, 17, 0, 0, 0, 4, 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