Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ac6936bb67a1341ae91c7e2b13520e54e2a263d2c41aa332f0ffd2895d9fa67

Tx prefix hash: 92d6ffaea6a0586574c7ccfbe0f3eb4456139bead3d30cb9409f2d7128c03263
Tx public key: 846da64dd78483a9d285f447d06a3902bdb9640aaa0d2bccf63b36f2aea89bb4
Timestamp: 1631637571 Timestamp [UCT]: 2021-09-14 16:39:31 Age [y:d:h:m:s]: 03:242:19:49:13
Block: 333737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 949007 RingCT/type: yes/0
Extra: 01846da64dd78483a9d285f447d06a3902bdb9640aaa0d2bccf63b36f2aea89bb40211000000105d7cc334000000000000000000

1 output(s) for total of 48.108060795000 dcy

stealth address amount amount idx
00: d7ce7a24160ecfbb027b941f6464564c766442d97012faf095187121d1b4526a 48.108060795000 688564 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": 333747, "vin": [ { "gen": { "height": 333737 } } ], "vout": [ { "amount": 48108060795, "target": { "key": "d7ce7a24160ecfbb027b941f6464564c766442d97012faf095187121d1b4526a" } } ], "extra": [ 1, 132, 109, 166, 77, 215, 132, 131, 169, 210, 133, 244, 71, 208, 106, 57, 2, 189, 185, 100, 10, 170, 13, 43, 204, 246, 59, 54, 242, 174, 168, 155, 180, 2, 17, 0, 0, 0, 16, 93, 124, 195, 52, 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