Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58b3f056b699c9c56baa2d8027c8a4238c2e6860fd7d0d883910b71c1d451f64

Tx prefix hash: 1b15cca955b61b60448bde79e38364be3c853a8016095ea7c0fc70e2ca0d2762
Tx public key: 8683107a9fe7709f682030ad120732c0dacc01cc479d623aa5cdc42c05c4de7c
Timestamp: 1727868636 Timestamp [UCT]: 2024-10-02 11:30:36 Age [y:d:h:m:s]: 00:220:18:31:16
Block: 1122796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157598 RingCT/type: yes/0
Extra: 018683107a9fe7709f682030ad120732c0dacc01cc479d623aa5cdc42c05c4de7c02110000001791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2668705365fe593d7e4fed8e924ef60f7010c3e5804b48c2acb75b60df0a78b4 0.600000000000 1605321 of 15

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": 1122806, "vin": [ { "gen": { "height": 1122796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2668705365fe593d7e4fed8e924ef60f7010c3e5804b48c2acb75b60df0a78b4" } } ], "extra": [ 1, 134, 131, 16, 122, 159, 231, 112, 159, 104, 32, 48, 173, 18, 7, 50, 192, 218, 204, 1, 204, 71, 157, 98, 58, 165, 205, 196, 44, 5, 196, 222, 124, 2, 17, 0, 0, 0, 23, 145, 225, 60, 4, 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