Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f768f17ef5302cc482c65df193047e178ab80b9253ba4eb4894f87a450b7614

Tx prefix hash: fb55f961a3349ece4d34fdb251967d2cd6049a3d01d4dfcba6ae1c896ec0927a
Tx public key: 05022ff2174693805724278b9cb4a00f6ebc2846e5a6e8827e58dc245b5ccb04
Timestamp: 1663894698 Timestamp [UCT]: 2022-09-23 00:58:18 Age [y:d:h:m:s]: 02:097:19:27:27
Block: 593742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591498 RingCT/type: yes/0
Extra: 0105022ff2174693805724278b9cb4a00f6ebc2846e5a6e8827e58dc245b5ccb0402110000000333af99f4000000000000000000

1 output(s) for total of 6.617384181000 dcy

stealth address amount amount idx
00: e3968aab4e1c2269e84c1af3c9d618a6c608a460f466bd67197c001a1d77def1 6.617384181000 1028553 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": 593752, "vin": [ { "gen": { "height": 593742 } } ], "vout": [ { "amount": 6617384181, "target": { "key": "e3968aab4e1c2269e84c1af3c9d618a6c608a460f466bd67197c001a1d77def1" } } ], "extra": [ 1, 5, 2, 47, 242, 23, 70, 147, 128, 87, 36, 39, 139, 156, 180, 160, 15, 110, 188, 40, 70, 229, 166, 232, 130, 126, 88, 220, 36, 91, 92, 203, 4, 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