Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9085a056cb744db2a26e6221a6c710e860235f6fdf63ee258fb8e01b69e89a2

Tx prefix hash: 6aca571a685216766402daca93723d51ecc9c761549213345354a914867c3223
Tx public key: 93cfe5fb076bdc5e204af644eacd6d06a3d5ab1ab1cfdc9cef9569ce9cb9cd99
Timestamp: 1662096710 Timestamp [UCT]: 2022-09-02 05:31:50 Age [y:d:h:m:s]: 02:260:10:19:50
Block: 579003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707415 RingCT/type: yes/0
Extra: 0193cfe5fb076bdc5e204af644eacd6d06a3d5ab1ab1cfdc9cef9569ce9cb9cd9902110000001a75e3f0e9000000000000000000

1 output(s) for total of 7.404961335000 dcy

stealth address amount amount idx
00: b7bb1bb1a08941bf1ecfd031dff5cd1b5a43f41f8e76d90909174fdaaec8e077 7.404961335000 1012429 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": 579013, "vin": [ { "gen": { "height": 579003 } } ], "vout": [ { "amount": 7404961335, "target": { "key": "b7bb1bb1a08941bf1ecfd031dff5cd1b5a43f41f8e76d90909174fdaaec8e077" } } ], "extra": [ 1, 147, 207, 229, 251, 7, 107, 220, 94, 32, 74, 246, 68, 234, 205, 109, 6, 163, 213, 171, 26, 177, 207, 220, 156, 239, 149, 105, 206, 156, 185, 205, 153, 2, 17, 0, 0, 0, 26, 117, 227, 240, 233, 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